【Current Behavior & Challenge】
In the Anaplan UX, the History feature does not currently respect the filter settings applied to a Grid Card.When a user maximizes a Grid Card or selects the entire grid to view History, the results include the audit trail for rows that are filtered out (hidden) on the screen.
【Business Impact】
For many large-scale transaction modules, we use filters to control row-level visibility (e.g., by department, region, or status).Because the History function reveals specific data changes—including "who," "when," and "what"—for these hidden rows, it creates a data privacy and governance risk.
To mitigate this risk, we are often forced to disable the History feature entirely on certain pages. This is a significant loss for our end-users, as History is a high-value feature that drives transparency and self-service within the platform.
【Requested Improvement】
We request that the History feature be enhanced to automatically sync with the active filter settings of the Grid Card.History results should only display data for the rows that are currently visible to the user on the screen. This change would allow us to maintain strict data governance while still empowering users with the full capabilities of the History feature.