Implement and manage semantic models

An analyst maintains a semantic model with 15 base measures. The business wants each measure to be viewable as Current, Year-to-Date, and Prior Year without creating 45 separate measures. Additionally, the YTD variant should display as currency while a new 'Percent of Total' variant must display as a percentage — all using the same underlying measures. Which combination of features should the analyst implement to meet these requirements with minimal measure duplication?

An analytics engineer has built two calculation groups in a Fabric semantic model: one named 'Time Intelligence' (containing items like YTD, MTD) and another named 'Currency Conversion' (converting measures to EUR and USD). Users report that when they apply a YTD calculation item together with a EUR conversion item on the same visual, the results are inconsistent depending on which group's logic runs first. The engineer must ensure that time intelligence is always evaluated before currency conversion is applied. What should the engineer configure?

A semantic model contains 40 base measures (Sales, Cost, Margin, Units, etc.). The business wants each measure to also be available as Year-to-Date, Prior Year, and Year-over-Year % variants. Rather than authoring 120 additional measures manually, you want a maintainable solution that applies these time-intelligence transformations to any measure the report author selects. Which feature should you implement?

You manage a composite semantic model that combines a DirectQuery connection to a multi-billion-row fact table in a Fabric warehouse with several imported dimension tables. Users report that high-level dashboard visuals showing yearly and monthly revenue totals are slow because every query hits the warehouse. Detailed drill-through visuals at the transaction level are used rarely but must remain fully accurate. What should you implement to improve the performance of the aggregated visuals while preserving detail-level accuracy?

You are building a composite semantic model in Power BI Desktop. A large fact table uses DirectQuery against a Fabric warehouse. A shared Date dimension is used both to filter the DirectQuery fact table and to filter a smaller Import-mode fact table for a different report page. You want cross-highlighting and relationship filtering to work efficiently against both fact tables without generating unnecessary queries back to the source. Which storage mode should you set on the Date dimension table?

You are optimizing a DAX query that produces a table of product categories with total sales. A colleague wrote it using SUMMARIZE with the aggregation expression placed directly inside the SUMMARIZE function, and profiling shows slow performance and high CallbackDataID activity in the storage engine. You want to rewrite the query so that the grouping is done efficiently and the aggregation runs in a proper row context without the performance issues of computing extended columns inside SUMMARIZE. Which approach should you use?

You are building a measure in a Power BI semantic model to display each product category's sales as a percentage of the grand total across all categories. The report page contains a matrix visual sliced by Product[Category]. Your base measure [Total Sales] = SUM(Sales[Amount]) works correctly per row. Which DAX expression correctly computes the percent-of-total for each category, regardless of which categories are visible in the current filter context?

You built a calculation group named 'Time Intelligence' with items for MTD, QTD, and YTD in an enterprise semantic model. Business users report that when they apply the 'YTD' calculation item to a non-additive measure such as [Distinct Customers], the result is misleading because a year-to-date accumulation makes no logical sense for that metric. You want the calculation items to apply only to a defined set of additive measures and return the unmodified base measure for all others, without creating separate calculation groups. Which DAX approach inside each calculation item expression best achieves this?

You build a calculation group named 'Time Intelligence' in a Fabric semantic model. It contains items like YTD, QTD, and PY. Users report that when they apply the YTD calculation item to a measure formatted as currency (for example, $#,##0), the resulting value loses its currency formatting and appears as a plain number. You want each calculation item to keep the formatting of the base measure it modifies. What should you do?

You are building an enterprise semantic model with more than 40 base measures. Business users want to view every measure with three optional adjustments applied through a single slicer: 'Actual', 'Currency Converted' (multiply by a stored exchange rate), and 'Rounded to Thousands'. You want to avoid creating 120 duplicate measures. Which feature should you use, and what DAX construct is required inside each calculation item?

An analyst builds a semantic model with a Sales fact table and a Customer dimension. Management wants a measure that counts customers who purchased in the current filter context but excludes any customer whose total sales fell below a $500 threshold. The measure must respect all report slicers (region, year). Which DAX expression correctly returns this count?

You are building a semantic model with a Sales fact table and a Date dimension marked as the date table. Business users need a measure that returns the rolling 12-month average of total sales, recalculated for whatever month is in filter context. The measure must divide the sum of sales over the trailing 12 months by 12. Which DAX expression correctly implements this?

An analyst needs a measure that calculates the total profit margin across all order lines in a fact table. Each row has a Quantity, UnitPrice, and UnitCost column, but there is no pre-calculated line-level profit column in the model. The measure must compute profit per row (Quantity * (UnitPrice - UnitCost)) and then sum those row-level results correctly under any filter context. Which DAX approach produces the correct result?

An analyst builds a measure to count high-value orders (amount greater than 1000). When they place this measure in a matrix sliced by product category and also apply an external filter selecting only the 'Electronics' category, they notice that a standard CALCULATE with a boolean filter on order amount unexpectedly overrides part of the existing category filter behavior in a comparison measure. They want the amount condition applied as an ADDITIONAL constraint that intersects with — rather than replaces — any filters already coming from the same column context. Which DAX function should wrap the filter argument to preserve the existing filter context and intersect the new condition?

You are building a semantic model for a subscription business. A Customers table and a Products table have a many-to-many association because a single customer can subscribe to multiple products, and each product has many subscribers. You have a Subscriptions table that contains one row for every valid customer-product pairing. You need a measure that correctly counts distinct customers per product without inflating or losing rows, following recommended star-schema modeling practices. What should you do?

You are building a semantic model for a retail company. A report page must display each product's rank by total sales within its own product category, so the top-selling product in each category shows rank 1, regardless of how the visual is currently filtered by category. You create a measure called [Total Sales]. Which DAX measure correctly produces the per-category ranking?

You are building a semantic model where users select a metric type from a disconnected slicer table named MetricSelector, which contains a single column [Metric] with three values: 'Revenue', 'Units', and 'Margin %'. You need a single measure named [Dynamic KPI] that returns the appropriate underlying measure based on the user's selection, and returns BLANK when no single value is selected. Which DAX expression should you use?

An analyst is building a measure for a Power BI report on a Fabric semantic model. The requirement is: return the total sales contributed only by the top 5 products (by their own total sales) within the current filter context, and the measure must respond correctly when a category or year slicer is applied. Which DAX pattern produces the correct result?

An analytics engineer is optimizing a slow DAX measure in an enterprise semantic model. The measure computes a ratio and references the same base expression [Total Sales] four separate times: once in the numerator, once in the denominator, and twice inside conditional logic that returns BLANK when sales are zero or negative. Profiler traces show the storage engine re-scanning the fact table multiple times per visual. Which change will most reduce redundant evaluation while preserving the result?

You are building a semantic model in Fabric with a fact table Sales and a marked Date table. Business users want a measure that compares the current visual's quarter total against the total from three quarters earlier, regardless of how the visual is sorted or which quarters are visible. You want to use the DAX window functions introduced for this purpose rather than classic time-intelligence functions. Which DAX function is the most appropriate core of this measure?