Is it possible to merge record ids from 2 separate but related tables?

  • 0
  • 1
  • Question
  • Updated 2 months ago
  • In Progress
Prior to today I had a user who managed records on her own table separate from the main records. She would enter information on her table, then give the same information to someone else in the company and he would enter it on the main table. I have created relationships and automations that will now take her entries and put them directly on the main table and update from her table. However there are 200 cases that have a record id on her table and a separate record id on the main table and they don't understand they are the same record in order to update the main table for the old records. I created a look up field on her table and identified the record id to each related case from the main table. It still doesn't know it is related. Is there a way to merge her record id with the main record id for the old cases?
Photo of Michelle Chapman

Michelle Chapman

  • 560 Points 500 badge 2x thumb

Posted 2 months ago

  • 0
  • 1
Once a record is created the Record ID# is set in stone, so you'll have to provide a secondary data point that would tell your automation to update based on a different value.

The path of least resistance would be to a flag these records with the RID in your table that it should correspond to in your table. Then - create a second automation to work in specific for these ones. If you have a value in this field, meaning it pre-dated your fix and you've had to manually intervene, then update the record using this 'correction' field that you added. Then have your current automation handle the rest, omitting anything that has a value in this 'correction' field. 

Chayce Duncan | Technical Lead
(720) 739-1406 |
Quandary Knowledge Base