Can merged products still be separated by proposal attributes?
We want to utilize the option “Merge multiple instances of this product into single line” on products, since it really helps clean up the product summary and makes things easier to read on the product summary.
However, in some cases we still need the same product to remain separated, because it could carry unique proposal attributes that should not be combined.
Is there a way to use “Merge multiple instances of this product into single line” on a product, but still force DealHub to split it back out if unique proposal attributes are present?
Page 1 / 1
Hi @jonasskaalen - I believe that the short answer is No. Once the system starts to merge items together, a single Product Assignment rule is referenced and all products will be merged. You might be able to reference a question that “collects” all of the unique details such as the example below, where a Collection question gathers all of the unique attributes and sets them to the products attribute.
I am curious about the desire to limit details presented in the Product Summary portion of the playbook. As this drives the data that is used in the CRM, more details and a higher fidelity view is typically preferred.
Output Documents and Product Summaries serve different purposes and can display information differently. Output Documents are customer-facing and typically use grouping and sorting to present a simplified view of what's been purchased. In contrast, the Product Summary retains all the detailed attributes and line items your internal teams need for processing and system integration. Using Proposal Summary Preview Templates, you can create rollup views that consolidate information for reps while maintaining the granular detail your reps and systems require behind the scenes.
I hope that this helps. I’d be happy to help take a closer look if there are additional details you’d like to share.
