-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NonUniqueObjectException when creating a new version of a finalized Versioned Folder #410
Comments
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). Both are imported from other place. |
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
The text was updated successfully, but these errors were encountered: