SAC Story breaks when Datasphere model is updated

[mikehoekstra1]

Hello

We have created a Datasphere analytic model with a live connection to SAC, and have created several Stories using this model. 

Recently we've added one new measure and one new dimension to the Datasphere model.  Nothing else was changed in Datasphere, but when subsequently running our Stories, most of the Story filters failed with the following message.  

In addition, numerous measures that we created in the Story have failed since those measures used those same dimensions that are no longer available.

Can anyone help with what happened here?  It would seem like a major issue if any Datasphere updates results in us needing to essentially recreate our existing Stories. 

Thanks for your help!

[ClemSteich · Accepted solution]

Hello,

This usually happens when a dimension/association/attribute has been unchecked and re-checked (added) at the analytic model level. After deployment, Datasphere will recreate a new internal ID for that dimension and it won't be recognized by the SAC story as the expected internal ID has changed for that object.

There might be other scenarios where that happens but that's the most common.

Regards,

Clément

[mikehoekstra1 · Accepted solution]

Thanks! This was indeed the issue and have been able to restore to a previous version and resolve the issue.

[hadar_k · Accepted solution]

Hi, thanks for the answer, we were facing the same issue, and indeed restoring to a prev. version did solve the issue. is there a wat to see the "new internal ID" in the DataSphere or maybe see an alert if this kind of behavior occurs ? for example updating on a change in this "new internal ID"?

[Martin_Kuma · Accepted solution]

Yes Hadar, unchecking an assoc in model-view, or removing / changing dimensions / measures will prompt for an warning -> stories will be affected.