Syncing Slicers and Configuring Drillthrough

This episode focuses on a practical PL-300 objective: Syncing Slicers and Configuring Drillthrough. Sync slicers carry a selected value across pages, while drillthrough moves to a detail view using selected context; they solve related but different navigation needs. The discussi…

A sales report has four pages. One summarizes revenue, another shows margins, a third compares regions, and a fourth contains transaction detail. A manager chooses the North region on the summary page, moves to the margin page, and expects North to remain selected.

Later, the manager chooses one product and wants to inspect the transactions behind it. Should both actions use the same navigation feature? More importantly, what evidence would show that the report meets the business requirement rather than merely appearing to work once?

Those questions sit directly inside the PL-300 scope. The course blueprint includes configuring sync slicers and configuring drillthrough navigation, including pages, filters, and buttons. The useful way to approach those skills isn’t to memorize where a control happens to appear. Begin with the outcome. Decide which filter context should follow the consumer, identify the report behavior that carries it, and then observe what happens under both normal and restrictive conditions.

Filter context is the set of filters affecting the data evaluated for a report visual or calculation. A visual is a report object that presents data or lets the consumer interact with it. If the regional slicer is set to North, that selection contributes to the filter context affecting the visuals connected to it.

The requirement might be for that regional choice to remain relevant across several report pages. That’s where synchronized slicers fit. Sync slicers can preserve filter context across selected pages, so a consumer doesn’t have to repeat the same selection whenever the report journey crosses a page boundary.

Drillthrough serves a different purpose. It passes selected context to a detail page designed for deeper inspection. Instead of preserving a general selection while the consumer browses several views, drillthrough begins with something selected in the current analytical view. The report then carries that context into a page whose purpose is to explain the selected item in greater detail. If a manager is looking at one product and needs the transactions associated with that product, a drillthrough page can receive that selected context and present the narrower result.

The distinction is about intent, not merely movement between pages. Sync slicers support continuity. The manager selected North and expects that choice to remain effective on the pages chosen for synchronization. Drillthrough supports investigation.

The manager selected a particular product because that product now needs closer inspection. Both mechanisms move filter context through the consumer’s report experience, but they answer different questions. One asks, “Which ongoing selection should remain with me?” The other asks, “Which selected item should I investigate on a purpose-built detail page?”

Suppose the sales director states the requirement this way: “When I choose a region, keep that region active on the revenue, margin, and product pages. When I identify a weak product, let me open a page showing its relevant transaction detail.” The regional requirement points to synced slicers across the selected pages. The weak-product requirement points to drillthrough navigation into a detail page. A single familiar feature shouldn’t be forced to satisfy both needs merely because both involve filters and pages.

This behavior belongs at the report interaction layer. A Power Query transformation changes data as part of query processing and refresh. It doesn’t represent a consumer choosing North while viewing a report.

The semantic model supplies the data structure and relationships that allow filters to affect relevant data, and DAX calculations are evaluated within filter context. Those layers matter to the resulting values, but the consumer’s movement between report pages is still a report-level interaction. Power BI service governance can affect how a published solution is accessed and consumed, but it doesn’t turn a query transformation into slicer synchronization or drillthrough navigation.

That layer distinction matters during troubleshooting. If the manager’s North selection doesn’t persist on a page where it was expected, changing an unrelated query step isn’t a focused response. Start with the visible failure. Which page did the manager leave?

Which page did the manager enter? What filter state was expected there, and what state actually appeared? Once that difference is clear, inspect the report configuration governing synchronization for those pages. A successful refresh doesn’t prove that the page interaction is correct because refresh and interaction are different kinds of behavior.

Now consider the drillthrough half of the requirement. The transaction page shouldn’t just be another destination with a convenient label. It needs to be meaningful when it receives the selected context. If the consumer selects a product, the detail page should reflect that product rather than presenting an unexplained broad result.

If the carried context is narrower than expected, the page may show only a small set of rows. If the combined filters exclude all matching data, the result may be blank. A blank page doesn’t automatically prove that navigation failed. It may be the correct consequence of the context that arrived.

That’s why you must define which context should travel. Imagine the manager first chooses North with a synced slicer, then selects Product A and drills into transaction detail. The business requirement might expect the destination to represent Product A within North. If so, both aspects of the context matter to the interpretation.

A detail result containing no transactions could mean there are no matching Product A transactions in North. It could also mean the report interaction or underlying model behavior doesn’t match the requirement. You distinguish those possibilities by examining the filter state and comparing the actual result with known data conditions, not by assuming that every blank is a defect.

Buttons can participate in drillthrough navigation, but the presence of a button doesn’t settle what context will reach the destination. The business meaning still comes from the selected context and the page designed to receive it. A button that appears usable is not, by itself, evidence that the resulting page is correct. The consumer must begin with an appropriate selection, use the intended navigation, and arrive at a page whose filtered result corresponds to that selection. That complete path is what needs validation.

Think of the button as part of the interaction design rather than a substitute for it. Its purpose should be understandable in the surrounding report experience. If a consumer selects a product and activates the detail action, the destination should support the natural expectation that the selected product is being examined. If the report instead arrives at a broad transaction page with no meaningful connection to the original choice, the consumer has moved between pages, but the drillthrough requirement hasn’t been satisfied.

The same discipline applies to synchronized slicers. Seeing similar slicers on two pages isn’t enough. The requirement concerns continuity of filter context across selected pages.

Test that continuity from the consumer’s point of view. Choose North on the revenue page. Move to the margin page that is intended to share the selection.

Observe whether the margin visuals are evaluated for North. Then move to a page that isn’t supposed to participate in that synchronized behavior. Its expected state should be based on the report’s actual design, not on an assumption that every matching-looking slicer must behave identically.

This is why there’s no universally correct synchronization choice for every report. Some pages may represent the same analytical path and should preserve the region selection. Another page may serve a different purpose and may not be intended to share it.

Synchronizing everything simply because the option exists can carry a selection into a page where the result is confusing or unnecessarily narrow. Synchronizing too little makes consumers repeat selections and can leave related pages showing different business slices. The requirement determines which pages belong together.

You can now design a controlled verification for the sales report. Begin with a normal case where matching data is known to exist. Select North and record the expected revenue and margin scope. Visit each page intended to preserve that regional choice and inspect both the filter state and the visual results.

The exact numbers aren’t the only evidence. You’re also checking whether the report clearly communicates that North remains active. If a page shows North-filtered values while the consumer can’t understand why, the calculation may be right but the experience can still be misleading.

Next, test the drillthrough path from a known product. Select Product A in a visual that provides the intended context. Use the configured drillthrough navigation and inspect the destination. Does the page represent Product A?

If North was also supposed to travel with the consumer, is the result limited accordingly? Do the displayed details agree with that combined interpretation? This is testable evidence at the layer where the behavior occurs. You’re proving what the consumer receives rather than treating the existence of a destination page or a successfully configured button as proof.

Then choose a deliberately narrow case. Perhaps Product B has only a few matching transactions in North. The destination should remain understandable even if it contains one row, a small total, or another narrow result. The page has to make sense under the context it was designed to receive.

A detail page that only looks coherent when hundreds of records are present hasn’t been adequately checked. Narrow results are not necessarily failures. They’re conditions that reveal whether the page communicates its filtered meaning clearly.

Finally, test a combination with no matching data. Choose a region and product combination known to produce a blank result. Follow the same navigation and observe the destination. The goal isn’t to force data to appear.

The goal is to determine whether the blank is consistent with the filters and whether the consumer can still understand what was requested. If the context is correct and no records satisfy it, then the blank or empty result can be valid. If the intended context didn’t arrive, the same blank appearance may have a different cause. The filter state is essential evidence.

Now suppose the normal Product A case works, but the narrow Product B case doesn’t. Don’t respond by changing several layers at once. Reproduce the failure and state the expected and actual behavior precisely. For example, “North remains selected on the source page.

Product B is selected. The destination should show Product B within North, but it shows a broader product result.” That statement is much more useful than “drillthrough is broken.” It tells you that navigation occurred and that at least part of the context may not have produced the expected result.

Inspect the control point closest to the symptom. For synchronized slicers, examine whether the relevant pages are part of the intended synchronization design. For drillthrough, examine whether the detail page, its filters, and the navigation path are aligned with the context the business asked to carry. Then consider whether semantic-model behavior explains the observed values.

A report interaction can pass context, but the model still determines how that context affects related data and calculations. The point isn’t to blame the model automatically. It’s to separate a report-navigation problem from a data-evaluation problem.

After a correction, retest the original failure and the normal case. This protects you from fixing Product B while accidentally disrupting Product A. Retest the synced region across every page that is supposed to share it. Retest the drillthrough destination with a common selection, a narrow selection, and a selection that returns no matching data. If the report is consumed under different relevant access or data conditions, validate the consumer experience in those conditions rather than assuming the author’s successful test represents everyone’s result.

A tempting shortcut is to stop when Power BI accepts the configuration. That only proves that a configuration action completed. It doesn’t prove that the filter context is the one the business intended, that the destination remains meaningful, or that the report behaves correctly when filters combine.

Correctness must be observed where the behavior happens. For this topic, that means watching the filter state, navigation path, resulting visuals, and consumer interpretation. Query output, relationship behavior, DAX results, refresh state, or access state may also help isolate a cause when one of those layers affects the final result, but they shouldn’t replace direct report-interaction testing.

Another shortcut is to test only from the author’s favorite starting point. Real consumers may reach a detail page after making several selections. Their resulting filter context can be much narrower than the context used during development. If the report is supposed to carry region and product, test region and product together.

If only product should travel through the drillthrough action, test that expectation explicitly. Don’t infer the requirement from whatever the current configuration happens to do. Write the expected context in ordinary business terms first, then compare the report against it.

Usability is part of that comparison. A technically filtered page can still confuse someone if the destination doesn’t make the active context apparent. The consumer should be able to interpret whether the details concern North, Product A, or the combination of North and Product A. This doesn’t require turning every page into a wall of filter information. It does require enough clarity that a narrow or blank result can be understood rather than mistaken for missing data, a failed refresh, or broken navigation.

Return to the director’s original request. The revenue, margin, and product pages need regional continuity, so the analyst uses synced slicers for those selected pages and verifies that the same regional context affects their visuals. The transaction page serves deeper inspection, so the analyst designs it as a drillthrough destination and validates that the selected product context reaches it. When the requirement calls for the region to remain relevant there too, the analyst verifies the combined result rather than presuming that one successful product test proves it.

The nearest alternative would change the experience. Ordinary movement to another page without the intended carried context may reach the right-looking destination while losing the analytical focus. Requiring the manager to reselect North on every page adds repetition and creates an opportunity for pages to represent inconsistent regions.

Sending every possible filter to the detail page can make results so narrow that consumers can’t interpret them. None of those choices is inherently correct or incorrect in isolation. Their suitability depends on the context the business wants to preserve.

When you encounter a mixed PL-300 scenario, reduce it to three decisions. First, state the requested consumer outcome. Second, identify the layer and mechanism responsible for that outcome.

Third, name the evidence that would confirm it. For synced slicers, the evidence is continuity of the intended filter context across the selected pages. For drillthrough, it’s a detail page whose result reflects the selected context and remains understandable for broad, narrow, and blank outcomes.

That approach prevents familiar controls from driving the design. You aren’t choosing sync because several pages happen to contain slicers, and you aren’t choosing drillthrough merely because the report has a detail page. You’re matching continuity and investigation to distinct business needs. Then you’re checking the resulting behavior through the eyes of the person consuming the report. That combination of requirement, mechanism, and observable result is stronger than any memory of where a setting appeared in the interface.

Sync slicers and drillthrough both carry context through a report experience, but they solve different problems. Synchronization preserves an intended selection across chosen pages. Drillthrough carries selected context into a page built for deeper inspection.

In either case, the configuration itself isn’t the final proof. Check the filter state, the resulting visuals, and whether the destination still makes sense when the result is common, narrow, or blank. Once you can state which context should travel, choose the report interaction that matches that requirement, and verify what the consumer actually receives, you can judge the solution by its behavior rather than by the presence of a setting or button.

Distinguish synchronized slicers from drillthrough navigation in terms of the context they carry. What source selection and destination result would confirm the design? Consult the matching episode reference when you are ready to inspect the terminology and reproduce the verification process. This lesson was produced by Bare Metal Cyber dot com.

Syncing Slicers and Configuring Drillthrough

headphones Listen Anywhere

More Options »
Broadcast by