Unfortunately a formula won’t work for this. Formulas only operate at the record level. When a formula is evaluated for a given record, the referenced cell values are always those from the same record. A formula can’t directly query the values of a cell from other records or tables.
That said, it’s still possible to get what you want, but it will require some tweaking to your base design. Because these referral URLs are effectively unique entities, and you want to track certain statistics about them, it would make more sense to build a separate table to contain them. I’ll call this sReferral URLs]
for now.
You haven’t described the process for generating new referral codes, so this will all be described somewhat generically, but when a new referral code and URL is generated for a given user, it should be added as a new record in that table, and then your {Eigen Referral URL}
field should link to that record.
When a download record is added that contains a referral code, it could trigger an automation to run. The automation would need to execute a script that would search for that referral URL in the tReferral URLs]
table and link to the appropriate record if found.
You could then use either a count or rollup field to count the number of links that each referral URL has, turning that table—or at least one view in that table, depending on what else you might want to do with that data—into a leaderboard showing how well each referral URL is performing. If you want to see that number back in the main table, a lookup field would do the job.
Unfortunately a formula won’t work for this. Formulas only operate at the record level. When a formula is evaluated for a given record, the referenced cell values are always those from the same record. A formula can’t directly query the values of a cell from other records or tables.
That said, it’s still possible to get what you want, but it will require some tweaking to your base design. Because these referral URLs are effectively unique entities, and you want to track certain statistics about them, it would make more sense to build a separate table to contain them. I’ll call this sReferral URLs]
for now.
You haven’t described the process for generating new referral codes, so this will all be described somewhat generically, but when a new referral code and URL is generated for a given user, it should be added as a new record in that table, and then your {Eigen Referral URL}
field should link to that record.
When a download record is added that contains a referral code, it could trigger an automation to run. The automation would need to execute a script that would search for that referral URL in the tReferral URLs]
table and link to the appropriate record if found.
You could then use either a count or rollup field to count the number of links that each referral URL has, turning that table—or at least one view in that table, depending on what else you might want to do with that data—into a leaderboard showing how well each referral URL is performing. If you want to see that number back in the main table, a lookup field would do the job.
Hi Justin,
Thanks! The automation is now working as i had in mind!
Bryan
Hi Justin,
Thanks! The automation is now working as i had in mind!
Bryan
Glad to know that you got the answer you were seeking! If you would, please mark my comment (the one above, not this one) as the solution to your question. This helps others who may be searching with similar questions. Thanks!