#Salesforce Revenue Cloud34 人正在讨论

Hi , 

I tried everything : new orgs, follow the steps, crazy settings, nothing worked. 

This is what worked for me :  

1. Created a new org  

2. Price Sync 

3. Under Edge MX , create new quote "Office Supplies" linked to "Office Upgrade" opportunity 

4. Added only the Software products mentioned in challenge 

5. Verify the challenge, Received Error : Laptop Pro Bundle is missing 

6. Added the Laptop Pro Bundle and re-verified the challenge 

7. WORKED.  

Hi @Swati Malkar

This is a known pain point in Spiff/ICM the tool is calculating off a live field (

Root cause: Spiff's plan logic is likely referencing Opportunity.CloseDate (or a similarly live-synced field) to bucket the deal into a payout period. When that field changes after calculation/payout, any report or re-run that re-evaluates the deal picks up the new value, creating a mismatch between "period paid" and "period the deal now says it belongs to." 

How to actually fix it a few layered options, roughly in order of how I'd sequence them: 

1. Snapshot the period at calculation time, don't derive it live. Add a dedicated field something like Commission_Period__c on the commission/statement record (or in Spiff's own statement object) that's set once when the statement runs and never recalculated from CloseDate again. Spiff does support adding effective dates on plans/logic and locking historical statements, so this should be a config change in Spiff's plan design rather than custom Apex — check that "lock historical statements" setting is actually turned on for closed periods.
2. Separate "Close Date" (sales-facing, editable) from "Commission Effective Date" (finance-facing, locked once a statement is generated). Reps and deal desk need to edit Close Date for pipeline/forecast reasons that's normal. The commission engine should never read that same field for historical periods once paid.
3. Treat post-payout edits as a reconciliation event, not a silent recalculation. If a close date changes after a statement already paid against it, that should trigger a clawback/adjustment workflow (a new adjustment line in the next period), not a retroactive rewrite of March's numbers. This is standard ASC 606-adjacent practice Spiff's audit-ready expense reporting is built around exactly this kind of compliant, locked-period model.
4. On the Salesforce side, if Opportunity edits are what's causing this, consider a validation rule or Flow that blocks/flags Close Date changes on Opportunities that already have a Commission_Statement__c (or equivalent) linked and Closed/Locked at minimum, notify Finance/RevOps rather than letting it happen silently.

I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

Hi @Christopher Strecker

, That's the missing piece. By assigning "Product Configurator API User" permission to my user, I was able to connect without any error. 

Hi @Uttej Cheedalla, 

A few things I would suggest checking: 

• Verify that the Context Definition Mapping is correctly mapped to the fields/attributes used in the qualification rule.
• Check whether the Lookup Table input values exactly match the values being passed at runtime.
• Make sure the correct Lookup Table is referenced in the Qualification Procedure and the procedure is active.
• If you're using a custom/extended context, verify that the mapping is configured as the default context mapping.
• Try running the Qualification Procedure using Simulation with a known product/input combination. This can help determine whether the issue is with the rule configuration or the runtime context.

Thank You.

Hi Vasu, 

Confirming this is exactly right, and it's a documented prerequisite for Advanced Configurator — easy to miss in the module. 

The error means the ConstraintEngineNodeStatus field setup wasn't completed: 

1. Create a custom field named ConstraintEngineNodeStatus (Text Area – Long, 5000 chars) on Quote Line Item, Order Product, and Asset Action Source. 

2. Give Edit access via FLS — the engine writes to this field at runtime. 

3. Go to Setup > Context Definitions, open your active Sales Transaction context, and add/tag this field so it's mapped for each entity (Quote, Order, Asset). 

4. Save and retry opening the Product Configurator. 

Reference:

This is a one-time setup step — once the field exists and is mapped, the configurator should open normally.

No, natively, ARM/Revenue Cloud doesn't let you search and add from "all products" the way Salesforce CPQ does..  

Natively, there's no way to search and add products in the Transaction Line Editor without going through Browse Catalog, and Browse Catalog is inherently catalog scoped; a product has to be catalog/category assigned to be searchable and addable there.  

For comparison: in Salesforce CPQ, clicking Add Product on the QLE pulls up a list of products based on your price book — there's no catalog concept in CPQ, so effectively every priced product is visible and pickable.

In ARM, Browse Catalog replaces that flow, and it's built around the catalog/category model by design — a product needs catalog assignment (plus price book entry, selling model, and indexing) to appear there.

Hi @Vasu Kasula

Did you try below options- 

1. Refresh the Decision Table Used for List Price 

2. Verify the Product Discovery Pricing Procedure and Context Definition 

3. Rebuild the Product Discovery Search Index