You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the problem that I cannot update the ReleaseNotes for a deployed version. Every time I update the ReleaseNotes in the "more" dialog of an existing version, the error message appears:
I also try to debug the api/version endpoint that is called but I have no clue whats wrong.
When I leave the version in the api call empty with Postman, the ERS says that it already has a record with the id:
{
"code": "E_UNIQUE",
"message": "Would violate uniqueness constraint-- a record already exists with conflicting value(s).",
"modelIdentity": "version",
"attrNames": [
"id"
]
}
So it would be perfect if you provide a fix for this issue or give me a hint where I can implement and provide a fix for the problem.
Thank You, Andreas
The text was updated successfully, but these errors were encountered:
Hello,
I have the problem that I cannot update the ReleaseNotes for a deployed version. Every time I update the ReleaseNotes in the "more" dialog of an existing version, the error message appears:
I also try to debug the api/version endpoint that is called but I have no clue whats wrong.
When I leave the version in the api call empty with Postman, the ERS says that it already has a record with the id:
{
"code": "E_UNIQUE",
"message": "Would violate uniqueness constraint-- a record already exists with conflicting value(s).",
"modelIdentity": "version",
"attrNames": [
"id"
]
}
So it would be perfect if you provide a fix for this issue or give me a hint where I can implement and provide a fix for the problem.
Thank You, Andreas
The text was updated successfully, but these errors were encountered: