Frame Agreements Won’t Load in Salesforce (CloudSense csfam): “Configure a default catalogue ID to proceed”

Solution

Issue

Agreements (Frame Agreement records) do not load and the UI stalls/spins. The following error is shown:

Visualforce Remoting Exception: Configure a default catalogue ID to proceed

Applies To

• CloudSense on Salesforce (reported package family: csfam; example environment: R36 MR3 sandbox)
• Frame Agreement loading (opening agreements from an Opportunity or directly via record URL)
• Scenarios where environments appear similar (including matching package versions) but differ in FAC Settings (csfam custom settings)

Root Cause

The failing org enforced a default catalogue requirement via FAC Settings:

• In csfam__fac_settings__c (FAC Settings), csfam__is_ps_enabled__c was set to TRUE.
• With csfam__is_ps_enabled__c = TRUE, the system requires "FA-defaultcatalogue" (default catalogue configuration/JSON). If it is missing, the Frame Agreement load fails with the Visualforce remoting exception.
• In a working org, csfam__is_ps_enabled__c was FALSE, so the default catalogue requirement was not enforced and agreements loaded normally.
• Different CloudSense package versions may enforce this requirement differently; however, this scenario is configuration-driven (no engineering fix is required).

How to Diagnose

1. Confirm the exact error message:
   • "Visualforce Remoting Exception: Configure a default catalogue ID to proceed"
2. Confirm the symptom:
   • Opening any Frame Agreement results in a stuck/spinning load.
   • This may occur when opening from an Opportunity, or directly via a record link such as:

3. https://your_instance.domain.com/lightning/r/<object_api_name>/<record_id>/view

4. Compare configuration between a working org and a non-working org:
   • Compare installed CloudSense package versions (to rule out version-only differences).
   • Compare FAC Settings values (csfam__fac_settings__c), especially csfam__is_ps_enabled__c.

Resolution (Configuration)

Choose one of the following approaches based on your intended behavior.

Option A (Most direct): Align FAC Settings to match a working org

1. In Salesforce, go to Setup.
2. Navigate to the CloudSense custom settings for FAC Settings:
   • Locate the custom setting/object: csfam__fac_settings__c (often displayed as “FAC Settings”).
3. Compare the value of csfam__is_ps_enabled__c between the working and failing org.
4. Set csfam__is_ps_enabled__c in the non-working org to match the working org (in the documented scenario, changing TRUE → FALSE removed the enforced requirement).
5. Save changes.

Option B: Keep PS enabled and add the required default catalogue configuration

If PS must remain enabled (csfam__is_ps_enabled__c = TRUE):

1. Ensure the required "FA-defaultcatalogue" / default catalogue configuration is present for the org.
2. Populate the required default catalogue identifier/configuration expected by your CloudSense implementation.
3. Save changes.

Validation / Confirmation

1. Re-open the same Opportunity and open an existing Frame Agreement.
2. Confirm the agreement loads normally and the error no longer appears.
3. Spot-check multiple agreements/users (if applicable) to confirm the behavior is consistent.

Notes / Common Pitfalls

• Two orgs can have the same package version but different behavior due to FAC Settings differences.
• Newer package versions may not enforce the same "FA-defaultcatalogue" requirement, so version comparisons can be misleading if the underlying setting differs.