I’m building a registration system where players sign up for an event with limited spots (18), and a waitlist starts for additional registrants. My challenge is maintaining a unique and consistent order for each player, especially because:
-
Duplicate Order Numbers: Currently, I assign an Order field by finding the last registrant’s order number and adding +1, but when multiple users sign up simultaneously, some end up with the same Order value, leading to conflicts.
-
I have the admin page that will be able to move players up and down (Order number +1 or -1), so the CreatedDate default type is not ideal for tracking positions if reordering is involved.
Suggestions for setting up a system that maintains unique order values across both automatic registration and admin-driven reordering?
Save the Current date/time:extract unix timestamp as their order number, then when an admin needs to put User #3 between #1 and #2, just set #3’s order to (#1’s order + #2’s order)/2 (average of the two) 
To show their actual place in line just show their index in a repeating group, or to get their index in a workflow search for the count users with a order number less than or equal to them 
1 Like
It worked! Thank you so much!

1 Like