Hi Jeff,
Thanks, that is what I did to make it work in the end.
What I couldn’t understand was why it was not working with CLEAR, but after some trial and error I think I figured it out. As I am using conditions on the bar button to compare the USC counter to be in range, it cannot compare CLEAR against a number so it must be removing that component on the fly.
I know originally you had suggested trying to use on single file to hold my data. However in my accident claim application it doesn’t seem like the best option for me. I have a number of situations where I think a separate table would be more appropriate
If there were multiple cars involved in the accident and multiple people (passengers) in the cars
I am thinking I will need to collect information on multiple cars, multiple drivers and multiple passengers, I think it will be best to create 3 tables to capture this and create a relation back to the main sheet.
If so then I am thinking
That’s fine. As I said, it really depends on your data. If it makes sense to split it into separate tables, then that’s what you should do.
I would still do everything from the single working table. You just need some extra columns. Here is what I would suggest:
Instead of linking everything back to your Users table, have a single master record that links to your users table, and then a series of “child” records that link back to the master record.
So for example, you might have 3 tables:
It’s only necessary to link the Accidents table to Users, and then both Vehicles and Passengers can link to Accidents.
The way you can achieve this is to have a user specific column in your working table that stores an AccidentID. At the start of the process, populate this column using a Unique ID special value.
In each of your 3 tables (Accidents/Vehicles/Passengers), include an AccidentID column.
At the end of the first stage where you have collected the basic accident info, write the Unique ID value into the AccidentID column when you add the row to the Accident table.
Make sure you do not clear that Unique ID user specific column from the working table at this point.
Then as you move on to the next steps of collecting vehicle and passenger details, you can re-use that same value for populating the AccidentID column when you add rows to the Vehicles and Passenger tables respectively.
This will give you a common ID that you can use to link everything together. So you’ll have something like:
Users
I am not able to find/add the “unique ID” component to my screen. Docs say it can only be added to certain screens that do add, edit, submit Not sure if it is because I am using custom action to Add Rows at final submit (custom button).
I think I got it. I think I need do it from the custom actions when I press the initial button.
yep!