We ran into an issue with our app where we started seeing the same IDs show up multiple times unexpectedly in our DB. These IDs were generated with the RAND(0,99999) function in Adalo magic text/formulas.
Turns out that all these entries with duplicated ids also had the same created_at timestamp. My hunch here is that the random number generator is using the created_at time as the seed.
We are now using the M30 API to generate shortids, like Victor mentioned. Thought I’d share in case others are running into this issue, and I second the call to upvote the request to make record_ids visible within the Adalo UI.
(edit: here’s a screenshot of my data with the repeated ids / timestamps)
We need the item to be created within Adalo so we can pass that new item to multiple pages and continually update it, but I agree that your method seems useful for other cases.
Would that be safe for multiple items created concurrently? Our issue is that the records had the exact same timestamp. The API call is super quick and very reliable as far as I can tell
I have never done stress test about this, but this is using internal update action with already opened linked data, so technically it should be faster.
If you don’t care about sequencing, you can use timestamp as random id, by multiplying first with large number such as 10,000,000 as date time is simply a number.
I don’t see how that would change anything if they are the exact same timestamps for each of the items (as displayed in my screenshot) – even if I change them to the number format, they will be the same number. I like the solution I have implemented above and was just trying to share the edge-case I ran into in case others did as well. No need to continue the convo.
