Introduction
When you create custom fields on Quote Line Items in Salesforce Revenue Cloud, simply adding the field isn’t enough. To use these fields in pricing procedures, display them in the Transaction Line Editor, or map values to Order Products when converting quotes to orders, you need to properly configure your Context Definitions.
This is Part 1 of a three-part series on mapping custom field values in Revenue Cloud:
- Part 1 (this post): Quote Line Item to Order Product
- Part 2: Product to Quote Line Item
- Part 3: Order Product to Asset Action Source (coming soon)
The Challenge
Let’s say you create a custom picklist field called “Power Requirement” on Quote Line Item with values like 110V, 220V, and 240V. You add it to your page layout and the Transaction Line Editor. When you try to save a value, it disappears! Why? Because the field isn’t in your Context Definition yet.
Context Definitions in Revenue Cloud act as the bridge between Salesforce objects and the Revenue Cloud engine. Without proper configuration, your custom fields won’t persist or map to related objects.
What We’ll Build
In this guide, we’ll configure a custom field to:
- Persist values in the Transaction Line Editor
- Be available for use in Pricing Procedures
- Map from Quote Line Item to Order Product when creating orders
Step 1: Create the Custom Fields
First, create your custom field on both Quote Line Item and Order Product objects. The field should have the same data type on both objects. In our example, we’re creating a picklist field called “Power Requirement” with values: 110, 220, and 240.
You can create fields through Setup, or use tools like Jetstream or Salesforce Inspector for faster deployment.
Step 2: Add the Attribute to the Context Definition
Navigate to Setup > Context Definitions > Custom Definitions and open your active Sales Transaction Context Definition.
- Click Edit
- Navigate to the Attributes page
- Select Sales Transaction Item node on the left (for line-level fields)
- Add a new attribute:
- Name: Power Requirement
- Type: Input and Output
- Data Type: Picklist (must match your Salesforce field type)
Important: For header-level fields (on Quote), use the Sales Transaction node instead of Sales Transaction Item.
Step 3: Create the Attribute Tag
Still in the Context Definition editor:
- Navigate to the Attribute Tags page
- Select Sales Transaction Item node
- Find your new attribute (use the filter to search for “power”)
- Click Add Tag
- Enter the tag name (typically same as attribute name)
- Click Done and Save
At this point, the attribute can be used in Pricing Procedures, but it’s not yet mapped to your Salesforce fields.
Step 4: Map to Quote Line Item
Now we need to connect the attribute to the actual Salesforce field:
- Go to the Map Data tab in your Context Definition
- Find Quote Entities Mapping
- Click the dropdown arrow > Edit as Object Mapping
- Click Map
- Use filters on both sides to find “power”:
- Left side: Your attribute under Sales Transaction Item (unmapped section)
- Right side: Your field under Quote Line Item (unmapped section)
- Click the circle on the left attribute, then click the circle on the right field
- Click Save and Publish
Now your field values will persist when editing quote lines!
Step 5: Map to Order Product
To carry the value to Order Products when creating orders:
- Go back to the Map Data tab
- Find Order Entities Mapping
- Click dropdown > Edit as Object Mapping > Map
- Filter for “power” on both sides
- Map the attribute (left) to the Order Product field (right)
- Click Save and Publish
Testing the Configuration
- Open a Quote and edit a line item
- Set the Power Requirement to “220”
- Save – the value should persist
- Click Create Order
- Complete the order creation wizard
- View the Order Product – Power Requirement should show “220”
Summary
To properly configure custom fields in Revenue Cloud, you need to:
- Create the field on both Quote Line Item and Order Product
- Add the attribute to the Sales Transaction Item node
- Create a tag for the attribute
- Map to Quote Line Item in Quote Entities Mapping
- Map to Order Product in Order Entities Mapping
What’s Next
In Part 2 of this series, we’ll explore how to set default values from Product records and have those values automatically populate on Quote Line Items when products are added to a quote. This involves cross-context mapping between the Product Discovery Context and Sales Transaction Context.