Forum Discussion
ChayceDuncan2
7 years agoQrew Cadet
If I'm understanding your question correctly - it sounds like what you have is a consumer table and tickets table in App X, and then a similar consumer and tickets table, but unrelated in App Z. Is that correct?
Are these apps in production? Your best bet if you want to stay out of the weeds is to consider making your 'key' field in your consumer table(s) into something like an 'Email'. That way - if the same consumer exists in App X, as well as App Z, you don't have to worry about having to locate the record ID# to relate the tables, you can send the email as the reference field and relate them that way
Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
Are these apps in production? Your best bet if you want to stay out of the weeds is to consider making your 'key' field in your consumer table(s) into something like an 'Email'. That way - if the same consumer exists in App X, as well as App Z, you don't have to worry about having to locate the record ID# to relate the tables, you can send the email as the reference field and relate them that way
Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base