I filter a table to get all rows owned by user A.
I then want to compare this set of data (the name column) to a second table to find the intersection of the two tables (table1.name == table2.name).
Here is the example:
All accounts owned by Bob (list of accounts) (a relation created by matching Bob)
All accounts owned by Triumph (list of accounts) (a regular table e.g. all rows are owned by Triumph)
The question being asked/answered:
How many accounts matching Bob also match Triumph?
This may have worked:
Triumph table with column called AccountName
Partner table with column - AccountName and column - RepName
Created a relation with Partner table (match on Bob) rel->BobsAccounts
Created “JL” a Joined List column on rel->BobsAccounts (joined on AccountName)
Created a Split List column on “JL”
Created a relation with Triumph table (match on the split list)
Seems to have worked, I get a subset of accounts.
Is this the correct method to compare the results of a relation against a table?
And will this scale to 1000s of records (current test was 100s of records against 2,000 records)?
You could shortcut this by just using a Lookup column instead, which will give you an array, instead of converting an array of values into a string using a Joined List, just to turn around and flip it back to an array with a Split Text.
Otherwise, I think you did everything else how I would.
Will totally try this since I have not used lookup in this manner! Love this functionality - does it scale?
I get frustrated with Glide more than I should, but, dammit, Glide can be spectacularly awesome at times.
Quoting Tom Petty - “it seems I remember the good times were just a little bit more in focus”
It should scale just fine.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.