Start a conversation Sign in
Start a conversation
  1. CloudSense Support
  2. CloudSense Articles
  3. Articles

CloudSense R37: “Generate Variants” Not Working from Offers (Incorrect/Legacy Variant Generation Page Opens)

Overview

After upgrading to CloudSense R37, clicking Offers → Generate Variants may fail to launch the expected variant generation experience or may open an older/legacy variant generation page (often perceived as a broken “Generate Variants” popup/publication page). This is typically caused by the ConfiguratorVersion setting being stored in a format that does not evaluate correctly in the routing logic.

This behavior is not resolved by restoring JavaScript libraries or source files; the underlying issue is the version value format used to route to the correct Variant Generation page.

Solution

Why this happens

The Generate Variants action decides which Variant Generation page to open by evaluating a version value:

  • It derives cscfga_version from your org’s ConfiguratorVersion setting.
  • Example routing rule:
If cscfga_version >= 35.3 → open VariantGenerationR35MR1
Otherwise → fall back to an older (legacy) variant generation page

If ConfiguratorVersion is stored in a non-comparable or non-matching format (commonly a patch/build format like 35.3.5, or an otherwise outdated/non-matching value), the comparison does not evaluate as intended and the system falls back to the legacy page—leading to the incorrect popup/UI behavior.

Step-by-step resolution: update ConfiguratorVersion to major.minor

  1. Locate the ConfiguratorVersion custom metadata record

    In Salesforce Setup, open your Custom Metadata for the B2C settings and locate:

    • Custom Metadata Type: B2C Setting
    • Record/Setting: ConfiguratorVersion

  2. Implementation detail: the record is stored in csb2c__B2C_Setting__mdt with DeveloperName = 'ConfiguratorVersion'.

  3. (Optional) Check the current value via SOQL

    select Id, csb2c__text_value__c
from csb2c__B2C_Setting__mdt
where DeveloperName = 'ConfiguratorVersion'

  4. Update the value to a major.minor format

    Set ConfiguratorVersion to a major.minor value that matches your installed Configurator line (example: 35.3).

    • Use: 35.3
    • Avoid: 35.3.5 (patch/build format) or other values that may not evaluate as expected in the routing comparison

  5. Save the change.

  6. Retest Generate Variants

    Return to the Offer and click Generate Variants again.

Expected result

After correcting ConfiguratorVersion, the action routes to the newer Variant Generation page (for example, VariantGenerationR35MR1 when applicable) instead of a legacy fallback page, and variant generation functions normally.

Verification checklist

  • Clicking Generate Variants opens the expected (newer) variant generation experience.
  • Variants are created successfully for a test Offer using your standard process.

Frequently Asked Questions

1. How can I tell if I’m hitting this specific issue?

You’re likely affected if, after an upgrade, Offers → Generate Variants suddenly stops working or appears to open an older/incorrect variant generation UI. Check the ConfiguratorVersion custom metadata value—if it’s in a patch/build format (for example 35.3.5) or otherwise doesn’t match the expected major.minor pattern, the routing logic may fall back to a legacy page.

2. What should the ConfiguratorVersion value look like?

Use a major.minor value (for example 35.3). Avoid patch/build formats (for example 35.3.5) because the routing comparison used by Generate Variants may not evaluate as intended.

3. Do I need to change code or update Visualforce pages to fix Generate Variants?

No. In this scenario, no code changes were required. Correcting the ConfiguratorVersion setting ensures the system routes to the correct Variant Generation page.

4. What if Generate Variants still doesn’t work after updating ConfiguratorVersion?

Reconfirm the ConfiguratorVersion value saved correctly in the B2C Setting custom metadata, then retest. If it still fails, capture what you observe (screenshots of the popup/UI behavior and any console/debug logs) and raise a new support request with your instance details and steps to reproduce.

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Matej Storga

  2. Posted

Comments