VEDA2 fatal error (unexpected case sensitivity)

[Antti-L]

I am facing the following fatal error:

Error Category: Fatal - Certain processes/commodities are declared with varying capitalization. Refer to the Error Details window for further information. The synchronization operation is unable to continue. Update or modify your model files before attempting to synchronize again. Starting from scratch is recommended.
Email the error log to support@kanors.com. You can open the error logs folder from Help -> Error Log menu.

I am confused by this. GAMS labels are case insensitive (by Latin alphabet): Casing of item labels does not matter. VEDA-FE respected that well, but now I am getting a fatal error.  I thought that VEDA2 would be consistent in this respect, because I remember some earlier discussions about it, and because in the VEDA online documentation I cannot see any mention that case insensitivity in models should be leading to fatal errors. Anyway, please find below the relevant error log entry, as requested.

Name : Veda.Common.KanLogger {3.1.3.0}
Time : 2024-08-30 19:07:15.1770
Type : ERROR
Machine / User : XXXXXXX / AD\XXXXXX
StackTrace : Certain processes/commodities are declared with varying capitalization. Refer to the Error Details window for further information. The synchronization operation is unable to continue. Update or modify your model files before attempting to synchronize again. Starting from scratch is recommended. ExecutionContext.RunInternal => Control.InvokeMarshaledCallbackHelper => Control.InvokeMarshaledCallbackDo
Message : System.IO.InvalidDataException: Certain processes/commodities are declared with varying capitalization. Refer to the Error Details window for further information. The synchronization operation is unable to continue. Update or modify your model files before attempting to synchronize again. Starting from scratch is recommended.
  at Veda.FrontEnd.SyncController.TagsProcessingFramework.DirectProcessing.ProcessCommodityDataValidation.d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  at Veda.FrontEnd.SyncController.TagsProcessingFramework.SyncControllerComposition.d__44.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
  at Veda.FrontEnd.SyncController.SyncControllerPresenter.d__57.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  at Veda.FrontEnd.SyncController.SyncControllerPresenter.d__56.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  at Veda.FrontEnd.SyncController.SyncControllerPresenter.d__47.MoveNext()

[AKanudia]

Veda2 is certainly case insensitive, like the earlier version and GAMS, but the current database platform (PostgreSQL) is case sensitive. We have to compromise in different ways to maintain case-insensitivity. One thing that we haven't managed to deal with yet duplicate declarations where the case doesn't match. Please see Information - Model - Manage Duplicates to spot any possible culprits.

[Antti-L]

Ok, thanks for the clarification.