SAP Datasphere graphical view deployment issue

[bohdan_kureshov]

Hello experts,

I have a graphical view in SAP Datasphere, which works fine. I have changed it many times and everything was fine. Suddenly I've got the error message: "Model could not be saved. Unexpected token 'c', "csn.query.column" is not valid JSON" or "Model could not be deployed. {"message":"Unexpected token 'c', \"csn.query.column\" is not valid JSON"}" depends on what I want to do save or deploy.

I can't save or deploy the view. I can't restore old version because of the same error (even if it's really old version). I've checked all predcessor views - everything is fine. When copy SQL code from this view to new SQL-view and try to deploy - everything is fine. If I do Save as new view and deploy it - it also works fine.

It's also affected successor views - they have the same errors. The last thing I did before the issue was changing size of measure with type decimal. I don't understand is it one time bug, so I just need to create a new view and replace all occurences of old view with this one, or do I have some issue which can break my model in future again.

[Avinash_Upadhyay_SAP01]

This seems like an issue out of the latest release. We used the lineage tool to identify the successor views which were errored out due to Design Time Error and then deployed all of them one by one. Finally, we re-deployed the impacted view and it worked out. Thanks!

[bohdan_kureshov]

Yes, did the same.
Also sometimes I coudn't just redeploy successor view, because of another error.
So firstly I've replaced my broken view with its copy in successor view, then redeployed both of them and only after that put original view as source in its successor.

[hudupa]

I attempted to re-deploy several views with design-time errors, except for one. I encountered the same error on that specific view. SAP is investigating the issue.

[hudupa]

This issue was resolved by first re-deploying the dependent views, which were causing design time errors. In cases where the dependent view was failing, we created copies of the views and replaced the main view with them. All objects are now active. Thank you all for your tips!
We hope SAP will find the root cause and send in the fix with the next update. 

[hudupa]

Hello,
I am experiencing the same error when activating an existing graphical view (Dimension). The view has been functioning properly and is utilized in multiple associations. Therefore, creating a new view is not a viable option for us. I am curious if this issue is related to SAP’s most recent update. We are currently using Version 2025.9.49 (build date 4/23/25).
I will submit a ticket to SAP.

[bohdan_kureshov]

Hello,
I've redeployed all successor view which had errors, and now it looks ok. But during that I've created a couple of copies of my first view and some of its successors, because sometimes successor (L1) view also has its own successor (L2) with error, so I can't just redeploy successor (L1). In that case I made a copy of successor (L1) replace original (L1) in (L2), redeploy (L2), redeploy (L1) and so on.

I understand that idea above is not an option for you, but did you try just redeploy every view in which your dimension view is used? Or are there a lot of views for that idea?

[atriquellc]

I had exacty the same problem, and I fixed it deploying all succesors of the view. I observed in the "dependency objects" list that some successors were in "runtime error" I deployed all and the problem was solved