Skip to main content

Query Settings

You can use the following settings to configure queries at the model level.

Factless settings​

  • query.factless.ignoreIncidentalfilter: Whether to ignore unrelated dimension filters in dimension-only queries. Disabling this may increase the time it takes to load filter screens in applications like Tableau. The default value is TRUE.
  • query.factless.useIncidentalFacts: Whether to allow dimension only queries to contain unrelated dimensions in the results. The default value is TRUE.

Language settings​

  • query.language.dax.bypassIsBlank: Whether to bypass IsBlank for metrics in DAX. Enabling this bypass can dramatically reduce some PowerBI query sizes. This can technically produce wrong results in some circumstances. The default value is False. For more information, see Known Issues.
  • query.language.dax.format.validate: Whether to enable the validation of the custom format string. The default value is True.
  • query.language.mdx.drilldown.allLevel.suppressDynamicMeasureGrandTotalExcel: Suppress totals for calculations containing dynamic members that will produce empty results. The default value is True.
  • query.language.mdx.drilldown.allLevel.suppressExcelHidden: Suppress drill-down cells not displayed by Excel. This reduces the number of queries, which may improve query performance but the results will be incomplete and may incompatible with other MDX clients. This also hides grand totals in some queries. The default value is TRUE.
  • query.language.mdx.drilldown.allLevel.suppressSubtotalExcelHidden: Suppress drill-down cells not displayed by Excel. This reduces the number of queries, which may improve query performance, but the results will be incomplete and may be incompatible with other MDX clients. This does display grand totals. The default value is FALSE.
  • query.language.mdx.slicers.allowHideNoData: Use filters, metrics, slicer lists, and/or rows and columns in the pivot table to determine which members in a slicer list will be hidden when 'Hide items with no data' is selected. This option uses the 'slicers.indicateNoData.X' flags to determine what is constrained. This may affect performance. The default value is False.
  • query.language.mdx.slicers.indicateNoData.useConstraints: Use filters in the pivot table and other slicers to indicate which members in a slicer list are affected by those constraints. This may affect performance. The default value is True.
  • query.language.mdx.slicers.indicateNoData.useMeasures: Use metrics in the pivot table to indicate which members in a slicer list have data in the metrics' fact tables. This may affect performance. The default value is False.
  • query.language.mdx.slicers.indicateNoData.useSelections: Use displayed slicer lists and rows and columns in the pivot table to indicate which members in a slicer contain data. This may affect performance. The default value is False.
  • query.language.mdx.subquery.limit: The limit of sub-queries generated for MDX queries. The default value is 500. If an MDX query fails the limit check, then the aggregate system would not attempt to build aggregates based on the violating query.

Other settings​

  • query.result.max_rows: The maximum number of rows that can be returned for a query. The default value is 200000.
  • query.slowQuery.cutoff: The query duration cutoff for a completed query to emit a SlowQueryEvent. The default value is 4 seconds.
  • query.planning.unsecureTotals.enabled: Whether to allow the unsecure totals flag to be applied to row security objects. The default value is False. For details about the Secure Totals option, see Creating a Row Security Object.