So, @mishav may have hi the nail on the head. I I manually entered the field recently, and added the 999. So perhaps that is it. However, if I sign up another user, it still ends up being ‘1’ as well, instead of ‘2’. Not sure if that affects the theory at all.
Yeah, this is interesting. For our convenience, it would be easier to have it sequential, just for knowing how many customers we have. And later on, how many orders have been fulfilled.
Maybe I am misunderstanding how bubble arguments work, but I don’t think we could use the unique ID any way, as I would need to use this information for dynamic data. So I couldn’t use the unique ID as a customer ID, because I then wouldn’t be able to get workflows to add this to invoices later, correct?
The problem I am seeing with ‘random strings’ is duplication. Wouldn’t I have to set up a bunch of other workflows to check that it is unique?
While checking for uniqueness would be a bit more complicated that anything else I’ve done with bubble so far, I could see away. Just search for the ID, if it is found, repeat the function. I guess I don’t see how to keep this cycle going until it finds one the is unique, if many cycles happen to be needed.