Set Value Of One Field If Another 2 Match
I'm trying to set a value in a field, if an email address matches an email address in a different field. For example, I have a field called Email and a report link called Merge: Existing Email. If the...
Forum Discussion
One solution is to generate a third table that combines a full list of unique emails across both tables. For concept - this table would be called 'Emails'. Basically the idea would be to use this table - and make the key field the 'Email' - and be a complete list of all unique emails combined from both tables. Then - make this email table parent relationship to both your leads - and this external source data referencing - and use the existing email fields as references.
The reason I'd suggest this method is the following - if set up properly you can:
Summarize the # of external records with that email
Summarize the # of Leads with that email
You can then pass that data back to Leads as a lookup - and in practice - if the # of External records using that email is greater than 0 or if the # of leads is greater than 0 - then your lead for example is for someone you've seen before
At the end of the day - what you're looking for is to identify each email as a unique entity - so you can summarize the different tables into it and play with the data that way.
Chayce Duncan | Director of Strategic Solutions
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
The reason I'd suggest this method is the following - if set up properly you can:
Summarize the # of external records with that email
Summarize the # of Leads with that email
You can then pass that data back to Leads as a lookup - and in practice - if the # of External records using that email is greater than 0 or if the # of leads is greater than 0 - then your lead for example is for someone you've seen before
At the end of the day - what you're looking for is to identify each email as a unique entity - so you can summarize the different tables into it and play with the data that way.
Chayce Duncan | Director of Strategic Solutions
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
Hi Chayce,
I think I understand the logic behind this, but I'm having some trouble putting it into practice.
I created a table called "Emails" and set "Email" as the key. I tried doing a table-to-table relationship with "Leads" with "Email" as the parent table. I select "Email" as the reference field. The lookup fields don't display for me on the next screen. I'm just seeing QuickBase Date Modified, Record Owner, etc... fields. I'm not sure the association was made correctly. I'm likely missing a step, but am not able to work through the summary part to understand that yet.
Thanks,
Quincy
I think I understand the logic behind this, but I'm having some trouble putting it into practice.
I created a table called "Emails" and set "Email" as the key. I tried doing a table-to-table relationship with "Leads" with "Email" as the parent table. I select "Email" as the reference field. The lookup fields don't display for me on the next screen. I'm just seeing QuickBase Date Modified, Record Owner, etc... fields. I'm not sure the association was made correctly. I'm likely missing a step, but am not able to work through the summary part to understand that yet.
Thanks,
Quincy