Issue with Schema Extension Before and After CU 4 Update Version 9.0.04 LTS Initial Situation (Before CU 4 Update): The schema extension had already been applied. When attempting to change a column field from False to True , the following error message appeared upon saving: “Another user has already made this change.” After some research, we discovered the CU 4 update and proceeded to install it. Following the update, the column field could be successfully changed from False to True . Situation in the Production System (After CU 4 Update): The CU 4 update was also installed on our production system. However, the schema extension was applied after the update. Unfortunately, the same error message appeared again: “Another user has already made this change.” Workaround: We were only able to resolve the issue by manually setting the field to True and then back to False via SQL. After this, the change could be made in the Manager without any issues. Concern: It seems that with every new schema extension after CU 4, we are forced to use a manual SQL workaround, which is not ideal. Question to the Community: Has anyone else experienced this behavior? Is there a permanent or official fix for this issue introduced with CU 4? Best regards Stephan

Issue with Schema Extension Before and After CU 4 Update

stephan sindern 2 days ago

Issue with Schema Extension Before and After CU 4 Update

Version 9.0.04 LTS

Initial Situation (Before CU 4 Update):

The schema extension had already been applied.
When attempting to change a column field from False to True, the following error message appeared upon saving:

“Another user has already made this change.”
After some research, we discovered the CU 4 update and proceeded to install it.
Following the update, the column field could be successfully changed from False to True.

Situation in the Production System (After CU 4 Update):

The CU 4 update was also installed on our production system.
However, the schema extension was applied after the update.
Unfortunately, the same error message appeared again:

“Another user has already made this change.”

Workaround:

We were only able to resolve the issue by manually setting the field to True and then back to False via SQL.
After this, the change could be made in the Manager without any issues.

Concern:

It seems that with every new schema extension after CU 4, we are forced to use a manual SQL workaround, which is not ideal.

Question to the Community: Has anyone else experienced this behavior? Is there a permanent or official fix for this issue introduced with CU 4?

Best regards

Stephan