Open pringinacio opened 1 year ago
Thanks @pringinacio - we'll look into this and squash it!
@pringinacio From the looks of the stack trace, you're using the 'import' feature to include data classes from somewhere else - are these from within the same versioned folder, or imported from an entirely separate model (we should be handling both, but just trying to recreate locally)
There are two Versioned Folders (A and B). B does not depend on any other Versioned Folder. A references elements (Use Data Element(s) of...) and data classes (Use Data Class(s) from...) of B.
Both are imported from other place. When importing B no fixes are needed. When importing A it is necessary to redo all external references to B (https://github.com/MauroDataMapper/mdm-core/issues/242). Although the 242 issue is resolved, the models where created before the issue was fixed, so not sure if this is impacting the current behaviour. I will perform some new tests to check if the issue #242 still continues or not.
Thank you - this is very helpful - we'll take a look
@jamesrwelch I confirm that #242 problem continues to exist.
Thanks for this. #242 definitely working with our existing use cases, but that's where imports are from within the same versioned folder. I'll do some more testing as I fix this issue 👍
Description
When creating a new version of a finalized Versioned Folder
(Create a New version -> New Version on the UI)
, a NonUniqueObjectException occurs. This does not occur on all finalized versioned folder, but as soon as it starts occurring, the solution is to delete all failing folders. And start all over.Steps to reproduce
e.g.
Expected behavior
A new "main" version of the folder is created.
Screenshots
Environment
Additional context
The stacktrace:
Server Error
We're sorry, but the server responded with an error message.
Details