Loading

Salesforce Reports: Fields Hidden by Field-Level Security Are Removed When an Editor Saves the Report.

Data pubblicazione: May 5, 2026
Descrizione

Let's consider a scenario involving three users:

  1. Admin user
  2. UK user (access limited to UK field)
  3. US user (access limited to US field)

The admin creates a report on a specific object, incorporating fields from both the UK and the US Users. Additionally, both the US and UK users have Edit/Manage access to the report folder. When the UK/US user saves the report, the fields that are hidden from the user are automatically removed from the report.

This behavior is expected because when the user opens the report, the report builder metadata only includes fields accessible to the user. Furthermore, since the user has permission to Edit/Manage the report, any changes made during saving are reflected in the metadata, resulting in the removal of fields inaccessible to the user.

 

Risoluzione

This behavior occurs because the report builder only loads fields accessible to the currently logged-in user. When an editor without access to certain fields saves the report, those fields are removed from the report metadata. This is a security design behavior — Salesforce does not allow report definitions to persist fields that are hidden from the saving user's profile. To prevent this, create separate reports for each user group, or manage report folder access so that only users with full field visibility can edit shared reports.

Numero articolo Knowledge

000989537

 
Caricamento
Salesforce Help | Article