FLS (Field-Level Security) Errors After Package Upgrade to R36 MR3

Symptom

After upgrading CloudSense packages to R36 MR3 (or later), users encounter Field-Level Security (FLS) errors when selecting products in the Solution Console. The errors occur because the upgraded packages now enforce object/field-level security validations that were not present in earlier versions.

These FLS errors do not appear in sandbox environments where the upgraded package is not installed.

Cause

Starting with R36 MR3, CloudSense packages added enhanced field-level security checks as part of Salesforce security review compliance. The packages validate that the running user's permission set or profile grants access to the CloudSense objects and fields being accessed.

Each customer implementation uses different custom objects and fields, so there is no universal list of required FLS permissions. The specific errors depend on which objects/fields your implementation references.

Resolution

Option 1: Grant FLS permissions (recommended for production)

Review the error messages to identify which objects and fields require access. Add the necessary FLS permissions to the affected users' permission sets or profiles.

Option 2: Opt out of enhanced FLS checks (quick fix)

If you need to immediately unblock users while you audit permissions, you can disable the enhanced FLS checks by creating a Custom Setting record:

1. In Salesforce, go to Setup > Custom Settings
2. Find JSON Settings (or csutil__JSON_Settings__c)
3. Click Manage, then click New
4. Set:
5. Name: security/enableEnhancedChecks
6. JSON Configuration: false
7. Click Save

This disables the enhanced FLS validation across the org. The system will behave as it did before the R36 MR3 upgrade.

Step 3: Verify

Navigate to the Solution Console and confirm that product selection works without FLS errors.

Additional Notes

• Option 2 (opt-out) is a quick workaround but reduces the security posture of your org. For production environments, Option 1 (granting proper FLS) is strongly recommended
• The enhanced FLS checks are enforced through common methods in the csutil package, so the opt-out setting applies to all CloudSense packages
• When auditing FLS requirements, compare the permission sets between a working environment (pre-upgrade) and the failing environment to identify the specific field access gaps