NUX Forms: Exception handling when duplicate code entered

When using forms to add to a list (where the code can be entered), users can accidently re-enter an existing code which triggers a model roll back, as it's considered a duplicate.


There's also no notification the model is rolling back so it looks like the app is spinning its wheels. This leads to confusion and potentially the user trying again (to no avail and another roll back).


Ideally, there should be some form of exception handling to prevent this scenario, including,

- notification that the code is already in use, and

- the option to accept that the data (inclusive of parent-child relationship) will be updated, or

- the option to cancel the process from running all together.

5 votes

New · Last Updated


  • This would be incredibly useful.


    A way to get around this would be to allow for automatic generation of a code on create, which has been suggested here (link below). The ability to add a form to a process would allow even more flexibility here.



    Forms are a fantastic new release, the above mentioned would help take them to the next level.

  • Are there any updates on this? When inserting list items from the back-end and then manually setting the code as a duplicate, an error appears almost immediately with no rollback - why is the same not possible via NUX? The resulting rollback/toast time this causes is significant - enough so that we are now abandoning the use of NUX Forms to get around this, it's too risky for a production model.

Get Started with Idea Exchange

See our Submission Guidelines and Idea Evaluation Criteria, then start posting your own ideas and showing support for others!