A user opens a report, for example a report on opportunities. His access rights to opportunities are restricted, and he does not see the opportunity ABC neither in the report, nor in the Opportunity work center view. However, when he uses the value help of the field Opportunity in the report, he can see the opportunity ABC.
Cloud For Customer
Reproducing the Issue
- Open the report from the assigned work center.
- Run the report and check all opportunities that are displayed. The opportunity ABC is not listed because the user has no access right to see this particular document.
- In the report selection, click on the Opportunity value help.
- The user sees the opportunity ABC listed here.
This report uses a joined data source. In data sources of this type, the access context of the user is not applied to value helps. This is done for performance reasons - when you join data sources, the system needs more resources to calculate every join and compile the data. So to avoid delays, the access context is ignored in value helps. This behaviour is consistent across all reports that are based on a joined data source.
This is the correct behaviour. The access context is nevertheless applied to the report data, so even if the user select the opportunity ABC from the value help, he will not see any data in the report if he is not authorized via his access restrictions.
Also note that value help in reports based on standard or combined data source will not display value ABC if end user is not authorized via access restrictions as in such case, access context of user will be applied to value help as well.
Report,Data Source, Access context, User, Value help, Performance, AP-RC-ANA, combined, joined, Access Restriction , KBA , unrestricted , access context , joined data source , AP-RC-ANA , C4C, ByD, Travel: Analytics Tools & Frameworks , How To