In Salesforce Revenue Cloud (not CPQ), the standard QuoteLineGroupId lookup field on Quote Line Item won't persist when set via the Transaction Line Editor, even though the Context Definition has an attribute (SalesTransactionItemGroup) mapped to it under the SalesTransactionItem node's Object Mapping; I've confirmed the attribute is Input/Output enabled and mapped correctly, ruled out any downstream trigger/flow overwriting the value (direct API updates to QuoteLineGroupId hold fine), and ruled out a data-type mismatch since other Text-attribute-to-Lookup-field mappings on the same node (Vendor__c, OEM__c, Contract_Vehicle__c) work without issue — the key difference with QuoteLineGroupId is that its target object, SalesTransactionGroup (mapped to QuoteLineGroup), is itself a node within the same Context Definition tree rather than an arbitrary external lookup, and I suspect there's a Node Relationship configuration between SalesTransactionItem and SalesTransactionGroup that's competing with or overriding the manual Object Mapping for that field; has anyone run into this specific case of a standard grouping field not sticking when its target is also a context node, and if so, where in the Node Relationship setup should I be looking to resolve it?
UPDATE: This is the response from SFDC Support as of 8/1/2026:
The behavior you are experiencing is a known limitation and is currently considered expected behavior in the Transaction Line Editor (TLE) within Revenue Cloud Transaction Management.
Root Cause
The QuoteLineGroup object is not configured as a valid custom foreign key target. Specifically, the entity definition for QuoteLineGroup does not include the canBeCustomForeignKeyTarget="true" configuration, which is available on most other standard entities. As a result, the TLE is unable to properly persist updates to the QuoteLineGroupId lookup field in the same way it does for other lookup fields.
This behavior is also consistent with the broader known limitation that standard Salesforce lookup filters and certain lookup field behaviors are not fully supported within the TLE, unlike on a standard Lightning record page.
This has been assessed internally as a feature request for the QuoteLineGroup object—specifically, to enable canBeCustomForeignKeyTarget, allowing the object to function as a standard foreign key lookup target within the TLE.
#Revenue Cloud #TLE #Quote Line Items #Quote Line Item #Quote Line Group #Quote Line Groups
Hi @Kieran Campbell - I don't think the Object Mapping is the issue. Since QuoteLineGroup is also a node in the same Context Definition, TLE is likely using the Node Relationship to determine the group and overwriting the QuoteLineGroupId during save. I'd start by reviewing the SalesTransactionItem to SalesTransactionGroup relationship and how it's configured to resolve group membership. The fact that API updates stick but TLE updates don't is a strong clue.
