The addition of Per User Data for the choice component is huge and helps me progress a little bit on a couple of side projects. Now individual users can create their own values for a choice component.
I’d like to bump this thread now because I’m trying to work on a gas logging app. The app allows a user to create a list of their own vehicles. Right now I create a UUID along with the vehicle, so the user can change the vehicle name while retaining the same unique ID. While creating a log (after filling the gas tank) I allow the user to select their vehicle. The choice component currently allows me to select the vehicle name and save that name to a log sheet. Ideally, I would like to save the UUID for that vehicle to the sheet, but display vehicle name to the user in the choice component. I will be doing stats and calculations on the form entries to track long term gas mileage and UUID allows me to keep all of the stats together for a vehicle, regardless if it was renamed. With the current setup, I can’t change the vehicle name without breaking stats. Storing UUID instead would allow me to use relations to pull the the proper vehicle name and keep all of the form entries for that vehicle together. I could use a lookup to get the UUID from the vehicle name, but a vehicle name change would still break the old log entries and a lookup would fail.
I do have a way around this by presenting a list of vehicles first, have them select a vehicle, then present the form button and pull in the UUID to write to the log. I’m not in a desperate need of this yet, but it beneficial.