.png){kind=logo}
Adding Row Numbers as a Column in Your Data Set
Hello, is it possible to add the row numbers in as a column? how can we use the row number to refer to? Thank you
Hello, is it possible to add the row numbers in as a column? how can we use the row number to refer to? Thank you
You can add a new column to use as row numbers by: 1. Scrolling to the right of your table and clicking Add column
OR
2. Opening any column's dropdown menu and selecting Insert right or Insert left to create a new column.Once you've added the column, you can: 1. Click on the column header
2. Select Edit column from the dropdown
3. Choose an appropriate data type for your row numbers
4. Save your settingsYou can then manually number your rows or use formulas to generate sequential numbers.
Sources:
Table columns overview | Documentation | Clay University
Insert Column Left, Right
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!
Hi Cindy, thanks for getting in touch. Row numbers are not directly usable in Clay, they're more of a reference for users, rather than within columns, etc.. Could you tell me a bit more about what you're trying to do?
Hi Mark, I’m trying to make an index coloum with a formula where it uses row numbers, because I want each row to have a different version of a prompt. Is that making sense?
Okay, so you might have 10 different prompts, for example, and would want to rotate through them? Rows 1–10, 11–20, etc.? Something like that? One idea would be to use the round-robin feature in Clay. https://www.clay.com/university/guide/round-robin-enrichment-overview The main use case is for assigning leads to sales. But the tool in Clay is more generic/versatile than that. You can use it to ensure balanced allocation of [stuff] to [other stuff]. So you could process through the table, and "assign" each row to one of Prompt1, Prompt2, Prompt3, etc.. Do you think that approach woul owrk well for you? Or are there more nuances of your use case where we'd need a different approach?
Hmmm this is something I could try, the concept is the the same let me try it, thank you Mark appreciate it
Okay, let me know how it goes! Candidly, this feature is not the most intuitive one in the app, so I'm happy to help if you hit any roadblocks.