Forum Discussion
AAS calculations not reflected in semantic model
- 1 year ago
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.
- 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