Symptom
Succession Ad Hoc Reports had several gaps (before b1508 release) in supporting field level permissions for both MDF as well Employee profile field level permissions.
• MDF Field level is supported in all MDF schemas (both EC and non EC and Talent Pool)
• Employee Profile field level permissions are supported on all Succession schemas.
Environment
SuccessFactors BIZX: Succession & Employee Profile adhoc report
Reproducing the Issue
Field level permissions were respected in an inconsistent manner i.e. if a role does not have view permission to any field (say risk of loss) then also users belonging to that role could see that field and data in adhoc report.
Resolution
-
Clients can now enjoy the same level of permission rigor in Ad Hoc Reports as in the actual application. For example, if a user is not allowed to view “Risk of Loss” on the Employee Profile, the same restriction will be carried over to the Ad Hoc Report schemas.
- Field level permissions are respected uniformly throughout the application.
-
It allows clients to share reports with managers and employees without having to worry about data privacy risks.
We can enable field level permission in MDF Succession & Employee Profile adhoc report by enabling the same via backend. There is no option to enable this configuration via Admin Tools.
To enable field level permission in adhoc report, create an incident on the portal so that support team can enable this feature from the backend.
Keywords
KBA , LOD-SF-SCM-REP , Reporting and Data Imports Exports , How To