When 2 users are trying to create a record at the same time, you will always have the probability of having doubles anyway. It’s hard to provide sequential numbering/coding etc. with multiple users.
@LeventK have you ever done something where you can make sure only 1 user can edit? I was thinking maybe like an action that could “request lock” workflow, and forces a sync… Then it’s under that users ownership for a period…
@Grant_Stead
I had once tried it with creating a slice of the table with only the key column and had set a LINKTOROW() action for the form saved event to open up the record in edit mode with another form view. The first form had been set to autosave. It seemed it was working but I was using a delayed sync and as first come first serve rule apply, I don’t think that it will work with multiple users anyway, anyhow.
I expect there is option to generate sequential entry
Sequential numbers are discouraged with AppSheet. Because each user is working with a copy of the entire data set, it’s easy for duplicate sequential numbers to be used. In short: sequential numbering is a bad idea in AppSheet. @LeventK posted a link to the doc that explains why. Please read and understand it.
When the database for the created info being printed, the shown lengthy complicated references as serial no. or identification shall be too hard to read and follow with others
I would put a sheet formula directly on the Excel sheet based on the row number… In that way you can ensure the numbers stay sequential without duplicate. However, keep in mind that the end user of the app would need to sync, before seeing this value.
If I have inline table, where there is entry, and the button add is available to add more line entry. is there is a way to make an auto Sr for a column I added as SN.
This column SN shall not be the key, the Key is unique key.
no issue to start again 1, 2, 3, 4 in each inline table linked to the main table each one under unique no.
@egmv_appsheet
There’s no way to provide sequential numbering whatsoever in AppSheet when multiple users are interacting with the app. The best possible approach is to have a physical column in the back-end sheet with an Arrayformula to ensure that each record in that table have a sequential order. Insert a column after your Key column (assuming that your Key column is in Column A). Give a temporary column header name i.e. XYZ, and format this column as Number i.e. #,##0
After adding this column, regenerate your table’s column structure and ensure that the column is in place in the table schema and it’s correctly imported as Number type. Return back to your back-end and instead of the XYZ header name, use this formula:
It does not work properly when it comes to creating a workflow right after saving a form. it returns a value like this order acceptance/NaN-V1.pdf. NaN is the number i used in sheets using array formula.