Calculated measure in linked measure group is not refresh after cube writbeck

Hi,

You could try to workaround this by making the measure physical see if this could work.
New define your query using method in Measure Tool – Making SSAS measures physical see if it makes difference.

Regards,
Lukas

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Users always get connection timeout problem when using multi subnet AG via listener. Especially after failover to another subnet ----Hot issues October

Hi ,
Thank you very much for your answer. I have made measure physical, but it didn't help.

In my cube C3 I have created measure group C3 with measure m1_m2 and MDX SCOPE:

But still when users write new data to measure m1 in cube C1 and deploy changes (writeback is committed):

New value in cube C3 is only in measure m1, but measure m1_m2 is not updated, it has old value:

But when I clear cache by query:
<ClearCache xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">;
<Object>
<DatabaseID>DEMO</DatabaseID>
</Object>
</ClearCache>

measure m1_m2 has correct value:

Do you have idea why SSAS works like this? How to force SSAS to refresh data for measure m1_m2 immediately after writeback on measure m1?

This is a big inconvenience for users :-(
Please help us. Thanks in advance!!!

Regards,
Dorota

Hi,

Thanks for the explanation and the pics, they are very helpful.

I currently have not found a good way to automatically refresh the cache, also it could impact the whole performance of the cube. I suggest you to try setting the storage mode of the M1_M2 measure group, set it to ROLAP, see if this works.

Regards,
Lukas

Hi,

Thank you very much for your answer. I have changed StorageMode to ROLAP for measure group C3 (measure m1_m3):

But It didn't help :-( Do you have any other suggestions what to do?

Thanks in advance!!!

Regards,
Dorota

Hi,

Thank you very much!!!

My Analysis Server version is 13.0.5850.14. (SSAS 2016). The production server version is 14.0.1.439 (SSAS 2017).
The problem occurs on both servers.

Thank you for your help in advance!!!

Regards,
Dorothy