A user receives the error indicating they do not have access to a field used in the report filter. What is the root cause?

A user receives the error indicating they do not have access to a field used in the report filter. What is the root cause?

• A. The user does not have access to the Age field
• B. The report is missing the Age field
• C. The data source is offline
• D. The user lacks permission to run reports in general

Answer: (A)

Field-level access controls determine which data elements a user can reference in reports. When a field is used as a filter, the user must be able to view that field’s data; otherwise the system cannot apply the filter and returns an access error for that field. In this situation, the filter relies on the Age field, but the user does not have permission to view that field. The issue isn’t that the report is missing the field, the data source is offline, or that the user lacks general report-running rights—the error is specifically about not having access to the field used in the filter. To resolve it, grant the user the appropriate read access to the Age field (or the security scope that includes it), or adjust the filter to a field the user can access.

Field-level access controls determine which data elements a user can reference in reports. When a field is used as a filter, the user must be able to view that field’s data; otherwise the system cannot apply the filter and returns an access error for that field. In this situation, the filter relies on the Age field, but the user does not have permission to view that field. The issue isn’t that the report is missing the field, the data source is offline, or that the user lacks general report-running rights—the error is specifically about not having access to the field used in the filter. To resolve it, grant the user the appropriate read access to the Age field (or the security scope that includes it), or adjust the filter to a field the user can access.