AAS calculations not reflected in semantic model

[jovanaim_pavlov]

Hello everyone,

I am experiencing an issue with my Power BI semantic model, and I’d appreciate your help.

Here’s the setup:

My semantic model is connected to:

1. Azure Analysis Services (AAS),

2. A SQL database (import mode), and

3. SharePoint files.

The model is published to Power BI Service, and two reports are connected to it.

The issue:
When I create a new calculated column in AAS, it does not appear in the semantic model. It was working until Tuesday last week! Also, I have another semantic model connected only to AAS where everything works fine—the calculated columns show up as expected.

Has anyone encountered this issue or can point me toward a solution? Any guidance would be greatly appreciated.

Thank you!

[v-echaithra · Accepted solution]

Hi @jovanaim_pavlov ,

Thank you for reaching out to Microsoft Community.

When your model is multi-source and connects to AAS via DirectQuery, Power BI can cache metadata about the AAS model. Schema changes like new measures or columns added in AAS might not be detected automatically.
Hence manually refresh Metadata, like force Power BI Desktop to reload the schema from AAS Sometimes, Power BI caches metadata for performance reasons. Try refreshing the semantic model in Power BI Desktop manually, then republishing it to the Power BI Service, and ensuring that the reports are reconnected to the updated version.
Check if the original AAS table is being referenced in any calculated table or measure within Power BI. If Power BI references a "stale" version of the table, it may not pick up schema changes.
If using a Gateway for on-prem SQL or SharePoint refresh, make sure there's no refresh conflict causing the model metadata not to sync. Since this was working until last Tuesday, it may be due to a recent update or change in your workspace, gateway, or credentials. You might want to check the Power BI Service refresh logs or Azure logs for any anomalies around that date.

If this helped, please mark it as the solution so others can benefit too. And if you found it useful, kudos are always appreciated.

Thanks,
Chaithra E.

[jovanaim_pavlov]

This helped! 😀
I manually refreshed the orginal .pbix that was the very first one published in that workspace (while the one that was having a problem was based on a semantic model created by publishing the original (very first) report). So for everyone who has a similar issue - Find the very first report of that workspace, download it, refresh it manually and republish it and then all other reports will work proprely.
Thank you very much!!!

[Visharavana]

Hi @jovanaim_pavlov 

• Cleared the Power BI cache
• Use tabular editor
  • Opened the model with Tabular Editor to check if the new column was hidden
  • It wasn’t hidden, but this tool helped confirm that the model was out of sync