RBC requested this enhancement
Problem:
Customers building reusable project templates (e.g., standard DDQs) link individual Q&A records in the content library to those templates for recurring-answer tracking. Duplicate Assistant currently has no awareness of this linkage. When a template linked Q&A pair is flagged as a near duplicate, there is no indicator distinguishing it from a non-linked duplicate, so the system or user may end up archiving the linked record and keeping the other. This silently breaks the template's connection to that record. The gap is not surfaced until someone opens or exports the template later and finds an unlinked question, at which point they must manually search the library to find and relink the surviving record.
Current workaround:
Users must manually check the project name field on each flagged Q&A pair to see if it is marked as a template, then manually designate that record as primary during the merge so it is retained rather than archived. This is fully manual and easy to miss at scale.
Requested enhancement:
Add logic to Duplicate Assistant that recognizes when a flagged Q&A pair is linked to a project marked as a template, and gives that record precedence as the retained/primary version during a merge, so template linkages are preserved automatically.
Business impact:
Prevents silent, hard to detect breakage of template integrity for customers using standardized project templates, reduces manual review burden, and avoids downstream errors in DDQ or RFP responses built from those templates.
https://rfpio.slack.com/archives/CK06N2JNB/p1787186477686869