You’re absolutely right — this is a real usability gap in managed production environments, and it affects almost everyone working seriously with Dataverse.
What you’re describing isn’t a lack of knowledge or a missed option — it’s simply missing functionality in the maker experience.
What’s actually happening today
In sandbox / unmanaged environments, makers benefit from:
In production + managed environments:
-
The Custom filter is either missing or ineffective
-
Makers are forced to use All
-
System tables flood the list
-
Search becomes the only workaround
-
Discoverability drops sharply as the environment grows
This is especially painful in tenants with:
Why this is a problem (beyond annoyance)
This isn’t just cosmetic — it has real impact:
-
❌ Slower development and support work
-
❌ Higher risk of selecting the wrong table
-
❌ Harder onboarding for new makers
-
❌ Poor experience in production support scenarios
-
❌ Increased reliance on tribal knowledge (“search the schema name”)
Sandbox productivity ≠ Production productivity, which is backwards.
Why “search” is not a real solution
Relying on search alone assumes:
In real production environments, none of that is guaranteed.
Filtering is fundamentally different from searching.
The feature you’re proposing makes sense
Adding a Managed / Unmanaged / System filter alongside Custom would immediately solve this.
For example:
-
✔ Custom (unmanaged)
-
✔ Custom (managed)
-
✔ System
-
✔ All
Or even just:
This would align with how makers actually work in production.
Important point: this is already solvable technically
Dataverse already knows:
This is purely a UX decision, not a platform limitation.
Current (imperfect) workarounds
Until Microsoft addresses this, people resort to:
-
remembering schema prefixes
-
exporting solution lists
-
using Advanced Find / solution explorer
-
building in sandbox and “guessing” in prod
None of these are good UX.
Where to raise this so it has impact
This is exactly the kind of feedback Microsoft does act on if it gains traction.
Power Platform Ideas portal
https://ideas.powerplatform.microsoft.com
Suggested title (something like):
“Add Managed / System table filters in production environments”
This is not a niche request — it affects:
Bottom line
You’re correct on all counts:
-
Sandbox has better table discoverability than production
-
Managed environments are unnecessarily hard to navigate
-
Filtering out system tables should be first-class
-
Search is not an adequate replacement
-
A Managed/System filter would significantly improve productivity
This is a valid, well-justified usability request, not a nice-to-have.
If Microsoft wants makers to work confidently in production environments, this is one of those small UX changes that would have an outsized positive impact.
