The stacktrace indicates that there is a unique constraint or index violation:
Duplicate column value violates its unique constraint: integrity constraint violation: unique constraint or index violation; SYS_PK_10651 table: "dgafamodule$failureanalysis2" (SQL State: 23505, Error Code: -104)
Any validations on the entity that might lead to this error?
Or there is an issue in the indexes for the entity and if there are no specific indexes added there might be an issue with the entity index data itself. In the last case the index should be rebuild or at least test the issue with a new entity to verify that this is the issue.
Hi Mario,
I solved this problem. You can read my answer here: https://forum.mendix.com/link/questions/98324
The UniqueConstraintViolations that we've been getting at various locations in our application, especially after storing content in FileDocuments after a long web service call, have been analysed by Mendix. They refer to network problems and TCP resets.
Could you let us know whether committing objects separately in-between solved the problem?
Found a solution that worked for me. I got this and then realized that I had a data grid as a starting point where I clicked NEW to create the context object that held the files. When you do this.. the context object is NOT COMMITTED yet. When you try to upload files, there must be a problem with trying to find an ID of the context object that causes this “unique contstraint violation” error. Once I fixed it so the context was committed, it worked
Thanks for the above Answers.