Preventing Duplicate Entries using Dynamic Data - Does not allow 'Editing' Existing Submission

@janna, yes the DDA feature would not allow you to edit your submission (from the server) if the identifier variable has already used that certain value. However, maybe you could use this approach to capture that identifier variable (recorded earlier) by following this post and storing it under the hidden variable:

You could then change that identifier variable value to something else when editing your submission so that the server would get a new value for the same and would not take the previous value to block your changes.

So the approach would be as follows:

  1. You store your ID as LHS.BF.OSK.002
  2. Try to edit your submission on the server (you are not allowed)
  3. Make necessary changes to your form and also change the ID from LHS.BF.OSK.002 to LHS.BF.OSK.002.1 or something that marks the change.
  4. Your submission is now unique and will be submitted to the server.

If you wish to see the original ID for any submissions that were edited, you could check the hidden variable value where we used the once() function to capture the original value entered which would be LHS.BF.OSK.002 in your case even through you have later changed it to LHS.BF.OSK.002.1 or whatsoever.

Hope this workaround works for you. But at the same time, let us also see if the community has some other easier workaround for you.