Join the Community

03 Feedback & Requests

03 Feedback & Requests

Improving Lookup Relationships for Enhanced Data Navigation

·

·

03 Feedback & Requests would be great to be able navigate within column data in a lookup relationship. how this would benefit: This would allow to lookup through relationships, or access enrichment column details and collections inside the lookup table, direclty from the parent, without need of creating extra columns or formulas into child that later can be then accessed in parent example use case: imagine you are in a company table that has enrichment fields, with collections inside then you are in the people table, with also enrichments and collections. In people table you have a lookup into company table, and you would like to access details in the columns from that lookup. Like Salesforce details in the Account table, you will have to move down into fields those datapoints you would like to read from other tables referencing the Account table example 2: have 2 different tables with domains that I need to normalize, so I add normalize into each table, so then I can do a lookup exact match (websites, linkedin profiles etc). Right now you need to create the extra text field "normalized domain " in the target table, because we can't navigate at that level

13 comments

Adnan M.
·
·
This is already possible. To see the collection in a cell with results, just click on it. To reference an object from a collection in a new integration, just type / to get the column drop-down, and go to that column and click on it to see the objects within the collection. Click on the object you want to reference.
Esteban L.
·
·
I mean all you mention, but a records you are accessing from a lookup relationship first
Adnan M.
·
·
Okay so you're asking for this functionality to extend to the Lookup integration.
1
Esteban L.
·
·
pseudo table1.enrichmentColumn.collection[0].property.getValue but from a lookup so table2, reference throguh lookup to table1 and then you want to do that within the lookup for example table2.normalizeUrl.normalizedURL == table2.lookupToTable1.normalizeUrl.normalizedUrl you can't do that, and same with any similar going through cell data from a lookup
Adnan M.
·
·
Gotcha. This would be super helpful and would eliminate the need for redundant columns.
1
Esteban L.
·
·
exactly 🙂
🎯1
Adnan M.
·
·
Also, why can't we write regular objects that are not lists, to another table? Makes no sense why they have this limitation that we NEED to start with a list.
Arturo O.
·
·
Hey Esteban L., thanks for the feedback, that makes sense. Not certain as to why nested objects aren't currently returned via the Lookups to allow for the association but one reason I can think of for now is the potential cell size limitation. I've shared it with the engineering team so we can revamp these tools in time! Adnan M., also appreciate the feedback about Write to table. Would like to clarify that a list is not Needed/Required for it to work, you can skip the field :D... We just forgot to add "(optional)" label next to that field although it's primary use is to extract and export an array. Here's a quick video with that example, but this integration will be receiving improvements soon too— Stay tuned!
Esteban L.
·
·
great thanks Arturo!
Channeled
APP
·
·
Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Esteban L.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Esteban L.!