Add a column with the proposal's Unique ID as it is a more reliable join key than proposal name/version.

Problem:

Due to size of our ProPricer database, when exporting data out of ProPricer using Integration Pro, we only pull records for recently created or modified proposals. We then must merge these changes with the existing proposal records that were pulled previously.

To merge the changes, we currently must use the Proposal Name and Version to determine which existing records across all tables were changed, so that those records can be replaced with the latest information.

However, this is a major problem when the Proposal Name or Version changes in ProPricer as that makes it so new records can no longer be mapped back to their old records (in order to replace them).

Solution:

Please add the ability to pull the proposal's Unique ID as a column in every table that includes the Proposal Name and Version columns. Since this Unique ID never changes, it will always be a reliable way to map new records to the old records which they will be replacing.

I attached a picture of the proposal's Unique ID column that I am referring to.