How to: Solve Common Inventory Use Cases with Filters
Last updated
Filters turn the Inventory from a list into answers. This guide works through one common use case end to end; the same pattern applies to most cleanup and governance questions.
Surface newly created Power BI reports in production that are unhealthy, excluding test artifacts, so they can be fixed before they impact business users.
Why it matters. New reports have had less time for validation, which makes early-life issues more likely: configuration gaps, performance inefficiencies, or incomplete modelling. Left unnoticed, unhealthy production reports degrade the user experience, increase refresh and capacity pressure, create downstream reliability issues, and reduce trust in production reporting. Reviewing them regularly lets your team intervene early.
Who owns it. Typically BI administrators, analytics platform owners, and data governance or Center of Excellence teams: the roles responsible for production health and standards.
Steps:
Open Control Tower and navigate to the team that contains your production Power BI workspaces.
Select Inventory to view all assets in scope.
Click Filters next to the search bar to open the Asset Filters panel.
Add rules that exclude assets whose name contains test, dev, or uat, grouped with OR so any match is excluded. If valid production assets contain these strings (for example, "evaluation" contains "uat"), add a rule or group to explicitly include them.
Give the filter a descriptive name (for example, production reports), click Save, then Apply.
Open the Reports tab and use the attribute filter to show only Unhealthy assets. Sort by creation date to focus on the newest ones first.
Last updated