How to Reference Row's Unique Identifier in Database Tables

Is there a way to reference a row's unique identifier? is it possible to expose the row id (similar to "created at" / "updated at" columns)?

10 comments

Channeled
APP
·
·
When working with data in Clay, there isn't a default unique identifier column for rows. However, you can specify which fields should be used as unique identifiers through the "Uniqueness Fields" setting. If you don't select specific fields as unique identifiers, Clay will use the entire row content as the unique identifier. Keep in mind that using the entire row as an identifier may result in duplicate records in your Clay table. Source: Salesforce Reports with Salesforce
Mathew I.
·
·
Person
Mathew I.
·
·
Curious what the ideal work around it -- creating my own unique identifier column is difficult bc rows don't know about each other
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Bo (.
·
·
Hey! 👋 I'm curious - what are you trying to accomplish with the row ID? Once I know more about your goal, I can suggest the best way to handle it! 😊
Mathew I.
·
·
I'm building an external API to track waterfall metrics by data source (i.e. success rates %, cost, etc) so I can project costs of future operations without having to manually track stats
Mathew I.
·
·
Tracking data by "row id" will allow me to filter out duplicate calls which can muddy the data
LuisArturo
·
·
Hey there Mathew thanks for sharing this jumping in for Bo here, if you are trying to create a unique ID to track rows in your table you can use a formula to accomplish this. We actually have a loom video that shows you how this can be done. https://www.loom.com/share/6999a6817f4e41448847ee5cd44e2645?sid=9a76b54b-2d10-4535-8489-5514ff938901
Mathew I.
·
·
Awesome -- thank you
Channeled
APP
·
·
Hi Mathew I.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: