Salesforce Revenue Cloud Configurator: "Enter an attribute picklist value that's in an active or draft state" Error During Amendment or Configuration Rule Operations

Identify the applicable cause from the symptoms described above, then follow the corresponding steps. Multiple causes may apply simultaneously.

---

## Cause 1: Attribute Picklist Values Are Inactive or Excluded at the Product Classification Level

These steps re-include picklist values at the classification level and confirm their status so the configurator can reference them during amendment or configuration.

1. Open App Launcher and navigate to the Product Catalog Management app.

2. Select Product Classifications from the home page.

3. Open the affected product classification record.

4. Click the Attributes tab.

5. Click the dropdown next to the attribute that triggers the error and select Include or Exclude Picklist Values.

6. In the Include or Exclude Picklist Values window, confirm that all picklist values required for the amendment or configuration are selected (included).

7. Deselect any values that are genuinely inactive and not referenced by existing quote line items or configuration rules.

8. Re-select any values that were inadvertently excluded but are referenced by existing records.

9. Save the changes.

10. If a picklist value must remain in Draft status for business reasons, change its status to Active before performing the amendment. Draft values are blocked by this validation at runtime.

---

## Cause 2: Missing Field-Level Security on Configurator-Related Fields

These steps grant the required field visibility so the Advanced Configurator can read and write constraint engine node state during rule execution.

1. Navigate to Setup > Object Manager and open Order Item (API name: OrderItem).

2. Select Fields & Relationships and locate the ConstraintEngineNodeStatus field.

3. Click the field name and select Set Field-Level Security.

4. For all profiles that use the Advanced Configurator, including System Administrator, ensure Visible is checked and Read-Only is unchecked.

5. Repeat steps 1–4 for the Asset Action Source object and all Revenue Cloud-managed fields on that object.

6. Navigate to Setup > Object Manager > Quote Line Item (API name: QuoteLineItem) and verify field-level security on all Revenue Cloud-managed fields for the relevant profiles.

7. Save all changes.

After saving, the profiles will have the field access required for the configurator to process constraint engine nodes without failure.

---

## Cause 3: Flow User Checkbox Not Enabled for Non-Administrator Users

These steps enable the Flow User permission so non-admin users can execute the flows that power configuration and amendment operations.

1. Navigate to Setup > Users.

2. Locate the affected user and click Edit on their record.

3. Find the Flow User checkbox (API name: UserPreferencesFlowUser) and select it.

4. Save the user record.

5. Instruct the user to log out and log back in for the change to take effect.

The Flow User checkbox grants the running user permission to execute flows in the context of configurator and amendment operations. Without it, flow-driven steps fail silently or return permission errors.

---

## Cause 4: Gateway Timeout During Configuration Rule Execution (Known Issues KI-69581, KI-67405)

These steps reduce rule complexity and operation scope to prevent platform timeout limits from being exceeded.

1. Reduce the number of products added simultaneously in a single Browse Catalog operation. Add products in batches of two to three at a time rather than in bulk.

2. Navigate to App Launcher > Rule Libraries and open the rule library associated with the affected product.

3. Review all configuration rules for circular references or overly complex constraint model language expressions and simplify where possible.

4. If timeouts persist after reducing batch size, retry the operation as documented in Known Issue KI-69581.

5. For timeouts specific to Auto-Add rules, review Known Issue KI-67405. This known issue documents that updating multiple nodes simultaneously in a Standard Configuration Auto-Add Rule causes failures. Modify the rule to target a single node per rule execution.

Simplifying rule scope and reducing simultaneous operations prevents individual requests from exceeding the gateway timeout threshold.

---

## Cause 5: CurrencyCode Not Passed Into the Product Configurator Component (Known Issue KI-71057)

These steps correct the Configurator Flow to supply the CurrencyCode value required for attribute validation.

1. Open App Launcher and navigate to Flows in Setup.

2. Locate the active Configurator Flow and click Clone to create a working copy.

3. Open the cloned flow and locate the Product Configurator Product Attributes component inside the Data Manager Screen Component.

4. Configure the component to receive the Currency Code value from the Data Manager Screen Component and pass it into the Product Configurator Product Attributes component as an input.

5. Save and activate the cloned flow.

6. Assign the cloned flow as the active configurator flow in Revenue Cloud configuration settings.

Passing CurrencyCode explicitly into the component ensures currency-based attribute validation has the required context and does not fail with an attribute picklist error.