Configure Multi-Instance Setup for Quote Line Editor
Use this article when you need more than one Quote Line Editor (BC - Quote Editor v2) on the same Lightning record page. Each instance can have its own field set, grouping mode, read-only state, import setting, selection Flow, and visibility rules.
Use this article when
Use this article for admin and page-builder work where the same record page needs multiple editor instances for different user groups or use cases. For general configuration, see Configure Quote Line Editor. For day-to-day user behavior, see Use Quote Line Editor.
Why multi-instance setup matters
- Show a full editable editor for power users.
- Show a compact editor for quick entry.
- Show a read-only cost-review editor.
- Show a summary editor with expanded text areas.
Required concept: Editor ID
Each editor instance must have a unique Editor ID. It scopes saved column widths, allows independent per-instance behavior, and prevents collisions between editors on the same page. If the Editor ID is missing or blank, the component shows a warning and does not render normally.
What can differ per instance
- Line-item field set
- Group field set
- Lookup source toggles
- Grouping settings
- Import enablement
- Read-only mode
- Selection Flow configuration
- Selected Items Flow read-only allowance
- Imported row lock condition
- Textarea expansion setting
Setup walkthrough
- Open Lightning App Builder for the target record page.
- Add the BC - Quote Editor v2 component more than once.
- Set a unique Editor ID on each instance.
- Configure field sets and behavior for each instance.
- Add component visibility filters where needed.
- Save and activate the page.
Visibility rules
Multi-instance setup works best with Custom Permissions granted by permission sets. Use component visibility filters so different users see the editor variant intended for them.
Column width behavior
Saved widths are stored client-side per editor instance using a key pattern such as bcPqpFieldWidthSettings:<editorId>. This lets one instance keep a different width profile from another for the same user.
Common gotchas
| Symptom | Likely cause |
|---|---|
| Two editors share widths unexpectedly | The same Editor ID was reused across instances. |
| An editor does not render | The Editor ID is missing or blank. |
| Visibility doesn’t behave correctly | Review Custom Permissions and component visibility filters. |