I am using the integration API Call in a column. It to generate unique IDs to avoid duplicates. Each time it is called it gives you the current number and increases by 1 (atomic operation) I am calling the API in a column and I get the following [image] The one in red 2000008 is my unique JOBID…

I strongly recommend using the Row ID column for unique IDs. This approach here will likely not work. Here Glide is deduplicating the calls to the service and sharing a cached result. You can differentiate the calls be adding the Job ID (for example) as a parameter to the API call.

Hi David, Thanks for clarification, I was trying to figure out the caching and it makes sense. Problem with the ROWID is that it’s not human friendly. I need to place it on invoices and workorders for clients and their clients. I’ll experiment with your suggestion.

[image] Dan_San: Problem with the ROWID is that it’s not human friendly. I need to place it on invoices and workorders for clients and their clients. Could you use an adjacent column for the human-friendly description, and reference that instead within your invoices and workorders?

[image] How do I create an auto-incrementing row number with Glide Tables? Community Resources This is a question that comes up a lot, so creating this topic to use as a reference. Typically, there are two distinct use cases when it comes to auto-incrementing row numbers.…

Hi Andy, Not sure what you mean here, this is what I was doing but I cannot guarantee that the number will be unique, that is my problem, everything I try results in duplicates at some point. This is due to race conditions. I open a form pull in the NEXT unique number but I cannot update it until…

Hi Thinh, Yes, I was doing the first method, but in a slightly different way, the issue is that if two applications (either 2 users, or the same user decides to open the form on his phone and laptop) open the form, they will get the same unique ID, as it is not incremented until you don’t save. Th…

To prevent what you call the race condition, I think you would have to use Make/Zapier for this, but then you would also have to query the table to see the “latest record”, which requires Business/Enterprise. My thinking is: Submit the record as usual through the webhook. Query the tables to see …

Hi Dan! I have a feeling that you may find this Live build recording (from Loqode school) interesting. [🛠️ Live Build Session - 31st January, 2024] In this Live Build Marco shows how to build custom search bar, create index numbers for items and generate unique incrementing numbers that…

hey @Nataliya_Kovaleva - unfortunately the techniques that Marco was using will not solve the problem here. Order numbers are still calculated on each users device, so if two or more users add an order at the same time, they will all get the same order number. @Dan_San - what about making the IDs u…

Hi Darren, I am actually using a different counter for each user in the profile and increment it. This drastically decreased my duplicates but I still get 1 every 2 days, I think it is because they are either using multiple devices or they are sharing their credentials. The solution that Marc…

API call not able to read it

Ask for Help

ThinhDinh March 19, 2024, 12:32am 5

Have you tried this method?

Topic		Replies	Views
Unique Counter to avoid duplicates Ask for Help	12	353	December 19, 2025
Auto Increment Ask for Help	4	2685	September 14, 2022
Unique Incrementor for each Glide Table Feature Requests	0	114	March 18, 2024
Auto Numbering Ask for Help	58	7841	April 18, 2025
How do I create an auto-incrementing row number with Glide Tables? Community Resources tutorial	54	10559	April 18, 2025

API call not able to read it

Related topics