Summary:
Enable Integration Pro to include the proposal's Unique ID as a column in every exported table that already contains Proposal Name and Version. This would provide a stable, non-changing identifier that customers can
To merge the changes, we currently must use to reliably match incoming proposal records with previously exported data.
Problem Statement:
Because the ProPricer database is large, Integration Pro exports only proposals that were recently created or modified. Customers must then merge those incremental exports into their existing datasets. Today, that merge
However, this is a major problem depends on Proposal Name and Version as the join key across tables. This creates a major reliability issue when either the proposal name or version changes in ProPricer, because updated records can no longer be matched to the older records
Solution:
Please add the ability to pull they are meant to replace. As a result, downstream data merges become error-prone, inefficient, and difficult to trust.
Proposed Solution:
Add the proposal's Unique ID as an available column in every table where Proposal Name and Version are currently included. The Unique ID should be exported consistently across all relevant tables and remain aligned with the associated proposal record for both new and updated exports. Since this identifier does not change over time, it should serve as the recommended join key for customers who need to merge incremental exports with historical data. This enhancement should pre
I attached a picture of the proposal'sserve existing Proposal Name and Version fields while adding the Unique ID as a more reliable matching option.
Benefits:
Improves the accuracy of incremental data merges across exported tables.
Reduces failures caused by proposal name or version changes.
Provides customers with a stable and reliable join key for downstream data processing.
Increases confidence in exported data and reduces manual cleanup effort.