Analytic Model was created with older version of the editor

[PMathieu]

After last update of SAP Datasphere one of our Analytic Model is break

We receive the message : Analytic Model was created with older version of the editor. Delete and recreate the Analytic Model.

It's impossible to edit the Analytic Model, we can't restore a copy of our JSON file exported before the transport in production

After investigation, we think it is caused due special characters in the technical name

When we try to redeploy the model, we see the message below in the log.

Review the following warnings: Column(s) (/BIC/C_AIE_143) of entity "SPACE001.VG_ISU_DEVICE" contains one or more of (/, \, ", .) character(s) and the same are replaced in the analytical model.

Some fields that are used start by  /BIC/.. these fields are come from BW infoObject or ADSO and worked fine before the update.

Only one solution rebuilt a big Analytic Model 😞

It is therefore noticed that SAP unilaterally changes the functioning of its application without taking into account that there are customers behind the application.

[PMathieu]

I would like to inform you about a regression issue we are currently experiencing. Unfortunately, this regression affects both our development (DEV) and production (PROD) environments. While reporting remains functional, it is no longer possible to modify AMs. This situation complicates things even more for AMs that are currently under development, as they have not yet been documented to allow their recreation. I took the initiative to contact SAP to explore the possibility of desynchronizing their updates between the DEV and PROD tenants. My goal was to avoid any impact on production and to be able to block a regressive update. Unfortunately, SAP's response to this request was negative.

[StefanArtini]

Hi Mathieu, we face the same issue on some of our Analytical Models as well. We get the same error message, but I think the special characters (that we have too coming out of our source HCM System) are not the issue. We have these characters /MAN/ in almost every AM and most of them are still working. Our Analytical Models on PROD are also working (for now...). We face the error message only on DEV

[StefanArtini]

We opened a ticket on that issue and have now a solution. We changed the technical names of assoziations in the facts and also the assoziation for one dimension before the disruption. After naming the technical names of the assoziations back to the original naming and changing back the assoziation for one dimension, the analytical models can now be accessed again without an error message. Maybe also a solution for you and way faster, than a complete rebuilt of the AMs

[aclauin]

We have same issue and I couldn't activate one analytic model because of the "/" in some dimensions attributes.
For one dimension, changing the technical names to remove the "/" solved the issue.
But other dimensions are so in use that we can't take the risk to modify them.
Good thing that SAP already found how to fix this.

[PMathieu]

Ticket 172360/2025 is open

[NilPeksen]

I've also just ran into the exact same issue after the latest SAP Datasphere update. It’s super frustrating that suddenly the model is flagged as being created with an older version of the editor, and the only suggested fix is to delete and recreate everything. We also discovered that special characters (like “-”) in technical names are causing trouble these same fields worked fine before.

I also tried restoring from an older JSON export and redeploying the model, it partially worked in my case. 
I hope this helps and if anyone else has found a better workaround, I’d love to hear it!

[jan_fetzer]

All, we are sorry to hear about the disruption caused by the latest release of the Analytic Model editor. We have identified the issue and have fixed it. The fix will be deployed to your system with the upcoming wave 04 deployment currently targeted for Wednesday, Feb 19. Br, Jan Fetzer (Product Management SAP Datasphere Modelling)