Today my reports just stopped refreshing. The core issue was the renaming of fields, which caused an error. A bunch of fields are affected:
id_2 > id_3
project_id_2 > project_id_3
organization_id_2 > oragnization_id_3
Why did these fields has been renamed?
Is it possible to send notification before these kind of changes? It is very unconfortable, when I have to explain to the managers, why the reports today are not working properly. We rely on these field names, it is not a good practice to rename them randomly.
This is not the first time, similar problem happened about 1-2 years ago.
Probably the field names have changed due to the upgrade of release 25.0 to release 26.0 on Invantive Cloud / Invantive UniversalSQL on the evening of March 23, 2026.
The names of Simplicate fields are automatically derived from Simplicate’s metadata and can change between major and minor releases.
Although we try to avoid unnecessary changes, typically especially with dynamic data models field and table names can change unexpectedly.
There are currently no plans to detect such changes between releases and inform beforehand, since a release is taken into production for all users at the same time.
In case individual data model stability is required, it is recommended to setup one of the on-premises products such as Invantive Data Hub to retrieve the data using a version of choosing. Use of a version specific configuration can mitigate some of these issues, but depending on the platform, the underlying data model may still change dynamically on the platform side (such as Simplicate, AFAS or Odoo).
Thank you for the reply. However I understand the reason, this is really “dangerous” to implement a new major version without ability to test before, or at least know, that it will happen.
I wish, if there would be a “test” environment, where we could find out the impact of the new release. what if not the structure, but the numbers or field content is changed? (format for example, truncated strings) which can lead changing the numbers without noticing it.
However I accept this fact, this is not a suitable approach for providing any reporting system.
I am really concerned about this topic, because it’s hard to explain to the management that “it is as it is” or “it randomly can happen to us”. As a reporting manager I am responsible for this, and it will ruin my reputation. That’s why I would like to have a solution, that will prevent or at least predict these kind of events. If I knew about the date before, I could communicate, that maintenance is scheduled, and issues may arise. That would be acceptable for me and for the management also.
For the cloud variant, there are currently no plans to offer such a sandbox or similar. It is recommended to assume that this can happen. Even if such environment would be available, the problem remains that many cloud suppliers do not offer it and continuously release and change namings.
To mitigate the risk somewhat, a local version can be used, but this does not completely remove the problem as cloud suppliers connected to can change their data models dynamically without prior notice.
At Invantive, this has been solved by ensuring that staff is available every day to resolve changing and unexpected conditions.
Thank you for the answer. I wish, if we knew the date of major release upgrades. IT Service providers just use this approach to notify their clients before. These upgrades are scheduled and communicated.