Blog Post
JustinTorrence
4 years agoQrew Cadet
Something to note is that this solution does not achieve full parity and as far as I'm aware the use case below is only achievable by Table to Table import. You cannot merge records using the built in Record ID# field using Pipelines if the Record ID# does not exist in the destination app. If you want to do this you'll have to use some other field as the key field, and if you do that you'll lose out on the automatic incremental id capability and will need to come up with a solution of your own. I'd love for this use case to be supported in bulk Pipelines or API. I've even got a UserVoice post open about it.