I have a question regarding Heroku Connect rows and Salesforce Sandbox refreshes.
Heroku Connect cares about how many unique rows are synced in a given period. Even if that row becomes unsynced, it still counts toward the total.
During a salesforce full/partial sandbox refresh, the entire org is swapped and the records are re-inserted into a new org (I believe with entirely new SFIDs).
The question is, does a sandbox refresh double the rows Heroku Connect "syncs" and if so, what is the best practice to not have the double counting?
The staging sandbox has 100 contact records in it (with SFIDs, 1-100). Heroku Connect is syncing 100 rows (SFIDs 1-100). The sandbox is refreshed, and the same contact records are uploaded to the new org, but given SFIDs (101-200). Heroku Connect by default will have 200 rows - though the desired outcome is a swap.
Heroku Connect can be configured to use a Unique Heroku identifier instead of using the SFID as the primary key.
This Heroku Unique ID can be included in the data fresh on the sandbox. If we used a Heroku unique id, would this allow Heroku Connect to pull the records from the refreshed sandbox without appending a new set of data?