An administrator of an organization is implementing Manufacturing Cloud Intelligence and various dashboards and is also setting up Advanced Account Forecasting. Why would an administrator configure Field-Level Security for the Advanced Account Forecast Partner and Advanced Account Forecast Fact objects?
Suggested Answer:
C
Explanation:
Field-Level Security is used to differentiate which forecast dimensions and measures individual user groups can view or edit.
Salesforce explicitly recommends configuring Field-Level Security on the Advanced Account Forecast context/set-use object and the forecast fact object to provide different user populations with separate levels of access to forecast data.
For example, a regional sales manager may be allowed to view and edit a regional adjustment measure while an account manager has read-only access---or no access---to that measure. Salesforce's Advanced Account Forecasting training provides this exact type of implementation example, where regional managers and account managers receive different visibility and editing rights to quantity, revenue, and adjustment measures.
Record-level sharing determines whether a user can access the Forecast Partner or Fact record itself. Field-Level Security operates at a more granular level and determines whether individual fields on those accessible records are visible or editable.
Therefore, the objective is not merely to grant access to the records; it is to establish separate visibility levels for forecast data.
Study Guide references/topics: Configure and Build --- Advanced Account Forecasting Security; Field-Level Security; Forecast Facts; Forecast Measures; Data Visibility.