I have a repeat that is giving me trouble using the field app. I have it configured such that for new surveys, previous repeat records become read-only once a new record is started. This works fine. I would like, however, to set it so that when a survey is loaded from the Inbox, users can add new records but cannot edit any of the previously existing records. I've tried using various combinations of "query allowUpdates=false allowAdds=true" for the repeat, but it doesn't protect the last entry being edited (i.e., if it's submitted with 4 records, record #4 can be edited when loaded from the Inbox) Am I missing something? Currently considering adding an additional species choice and setting constraints to force users to enter a dummy species and count for the last entry before submission.
Update: I stripped my xls form down to not include any of the readonly or required coding, and it would appear that the allowUpdates prevents changes to my select_one question. However, for the count, it allows the entry to be changed, but once the user submits the survey, those changes to repeat values are not kept. So it does protect the values from updates, but by allowing the user to seemingly change it, it becomes problematic as the user may think they changed it.
XLS attached
