#Revenue Cloud토론 중인 항목 74개

Hello everyone, 

Im having a issue where im unable to deploy between two orgs due to the error: 

│ ContextDefinition       │ extendedSuraInsuranceContext   │ Cannot deploy Context Definition 'extendedSuraInsuranceContext' with release version '264.4.4' to an org with older release version '262.14.13'. This definition was created in a newer release and cannot be deployed to older orgs.

Both orgs, have Digital Insurance Packages and Salesforce Industries, where specifically the subtype of the orgs, despite them being the same "Insurance" wont let me deploy due the error previously mentioned. 

Already went with support, and they told me to try deploying these components manually to a org which i dont have access to. 

Also, having these orgs (Dev and build) with two different versions 264.4 and 264.11 

Has anyone had a similar issue? Is there any other suggestions to try on this case? 

Best, 

I have require rules that live in a constraint model that automatically adds different products based on the type of bundle that is added.

I needed to add a new product to the rule so that we can add it to the rule. However when we added a new item via "New Item" in the visual editor: 

And tried to add a bundle to the quote afterwards, the quote lines were not added and instead threw the following error: 

The item was added as a standalone product, and not as part of a bundle.

Tried commenting out the product in the CML editor which deleted the product from the model but my suspicion is that it has created other definitions in the backend that is now tripping up the pricing procedure. 

My questions would be

1. What is the correct way to add a new product to the index if the product was not already showing?
2. Has anyone ever into this issue before?

#Revenue Cloud  #Option Constraints @* Salesforce Revenue Cloud *

Hi everyone,

I'm working on a Revenue Cloud implementation with two sandboxes (both refreshed from the same production org, at different times). In Sandbox A, activating an Order correctly creates Asset records from the OrderItems. In Sandbox B, the exact same flow (Quote → Contract → Order → Activate) leaves the Order in Status = 'Activated' with zero errors, but no Asset is ever created — and querying Asset in that sandbox returns 0 records, period, in its entire history.

What I've already ruled out (identical between both sandboxes):

• RevenueManagementSettings, OrderSettings (all flags match, including enableEnhancedCommerceOrders=true, enableAutoAddDerivedAsset=true)
• PermissionSetLicense for Revenue Cloud User / Fulfillment User / Billing / Business Rules Engine — all Active
• Extended ContextDefinition mapping for Order/OrderItem vs Quote/QuoteLineItem — byte-for-byte identical counts
• No custom Apex triggers or Flows on Order in either org — it's the pure standard "Activate" action
• No AsyncApexJob/BackgroundOperation errors around the activation — nothing seems to even attempt the asset generation step
• TransactionProcessingType: the broken sandbox had zero records while the working one had one marked default (Business Rules Engine). I created a matching record via Tooling API, but the issue persists.

Has anyone run into a case where Asset-Based Order Management (or whatever gates Order→Asset generation) is silently disabled at the org level in a way that doesn't show up in any Settings metadata, Tooling API object, or PermissionSetLicense? Is there a one-time, irreversible enablement step (like "Enable Contract, Asset, and Subscription Management") that a sandbox refresh could leave off even when everything else looks provisioned?

Any pointers on where else to look (or whether this needs a Support case) would be hugely appreciated — this is blocking QA testing for a client go-live.