When a custom lookup field is added to the QuoteLineItem object pointing to another object (such as Asset or a custom object) and a lookup filter is applied (for example, filtering Location records where the parent Account ID equals the Quote Line Item's Quote Account ID), the lookup functions correctly on the individual QuoteLineItem record detail page. However, when the same field is used in the Revenue Cloud standard Transaction Line Editor (TLE) or the Quote record's Transaction Line Item related list via inline edit, the lookup search returns zero results or the field value gets cleared/reset after selection.
This behaviour is a known limitation of the Revenue Cloud standard Transaction Line Editor (TLE). Lookup filters applied to custom lookup fields on QuoteLineItem are not fully evaluated in the TLE inline editing context. The following options address this issue:
Cause 1: Lookup filters not supported in Transaction Line Editor inline edit mode
The TLE does not pass the required context (such as the parent Quote's Account ID) to evaluate dependent lookup filters during inline editing.
1. Navigate to the affected Quote record.
2. Open the QuoteLineItem record directly by clicking the line item link (not using inline edit in the TLE).
3. On the QuoteLineItem record detail page, use the custom lookup field — the lookup filter evaluates correctly in this context.
4. Save the record from the detail page.
Workaround A — Use the QuoteLineItem record detail page editor:
1. Instead of editing lookup fields inline within the TLE, click through to the individual QuoteLineItem record.
2. Edit the lookup field on the record detail page where the filter criteria are fully evaluated.
3. Save the record.
Workaround B — Remove the lookup filter and enforce filtering via validation rule:
1. Navigate to Setup > Object Manager > Quote Line Item [QuoteLineItem] > Fields & Relationships.
2. Select the custom lookup field (e.g., Location__c or Asset__c).
3. Remove the lookup filter from the field definition.
4. Save the field — the lookup now returns all records in the TLE without filtering.
5. Navigate to Setup > Object Manager > Quote Line Item [QuoteLineItem] > Validation Rules.
6. Create a new validation rule that enforces the same business logic (e.g., ensure the selected record's Account matches the Quote's Account).
7. Set the error condition formula to evaluate the relationship, for example:
AND(
NOT(ISBLANK(Location__c)),
Location__r.Account__c <> Quote.AccountId
)
8. Set the error message to: "The selected Location must belong to the Quote's Account."
9. Activate the validation rule.
10. Test by selecting a non-matching record in the TLE — the validation rule prevents save with a clear error message, while the lookup now returns results.
Workaround C — Use a Flow or Quick Action for field population:
1. Create a Screen Flow that queries the target object filtered by the Quote's Account ID.
2. Present the filtered list as a picklist or lookup component within the Flow screen.
3. On selection, update the QuoteLineItem lookup field with the chosen record ID.
4. Add the Flow as a Quick Action on the QuoteLineItem object or embed it on the Quote Lightning page.
005389635

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.