A report that runs for some users but not others, and that depends on a custom filter, points to access to that filter. The correct explanation is: users lack access to the custom filter ' s security class. A custom filter can be protected by a security class, and users who do not hold it cannot execute a report that relies on the filter. The report ' s data source is Chronicles, which is correct for Workbench, so the source is not at fault, and SlicerDicer has no role in a Workbench filter. The developer should compare the classes of a working user and a failing user, identify the missing class and ask the security administrator to grant it if the user should have the access. Where the answer also describes other needs, such as export permissions, the relevant setting in the report should be enabled and verified. Testing with an affected user confirms the resolution.
[Reference: Cogito Fundamentals – Reporting Workbench: Security Classes for Custom Filters in Workbench Reports, ===============, ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit