Filtering is showing what you’ve filtered - so from this perspective its accurate. If you allowed the user to change filters, then they need to understand the complexity behind those changes (but agree it is complex).
The only way you can hide this, that I am aware, is to build your own Data Page to use for Explore Data / Insights.
- You would do the filtering in the data page definition (hidden from the user and Insights)
- Data page would have to have Allow querying any column (Pega connection only) checkbox unchecked (not queryable)
- Then in Explore Data (from App Studio / Design Time version), you can run Insights directly on data pages.
- They do have some limitations on them, as they are not queryable, but that would hide the filters you applied from users.
I outlined this in the response to a Knowledge Share I posted: Some insights into Insights (and Explore Data) - #27 by MarcCheong
- The link should take you directly to the comment and image i posted
