Forum Discussion
Migrating AAS models to Power BI Fabric / Capacity - setup incremental refresh post migration?
- 1 year ago
Here's one of the ways
Enhanced refresh with the Power BI REST API - Power BI | Microsoft Learn
In general partition management in semantic models is very much the same as it is in SSAS. You can issue your XMLA queries from whichever client you prefer (SSMS, PowerShell, Power Automate etc)
When the datasets were in AAS, we were updating only recent partitions of the tables into the AAS model.
Reports were a live connection against AAS model.
After migration to power bi, i am assuming the power bi semantic model needs refreshing somehow to get the new updated data.
After migration - if i just manually refresh the semantic model or put it on a refresh schedule -- i am not really sure what partitions are being updated, or if it is always a full refresh going that route?
If i do not want a full refresh every time, what are my options?
I am not too familiar with tabular editor - i know we can manage partitions in there, but that doesn't drive what partitions get refreshed in the service does it?
Here's one of the ways
Enhanced refresh with the Power BI REST API - Power BI | Microsoft Learn
In general partition management in semantic models is very much the same as it is in SSAS. You can issue your XMLA queries from whichever client you prefer (SSMS, PowerShell, Power Automate etc)
- tbyberg1 year ago
Helper I
Thanks,
Yes, it does look the same.
We are utilizing a logic app to refresh specific partitions for the AAS models.
Those processes could easily be converted to use the xmla endpoint.
I was looking to utilize the more automated partition management via the incremental refresh you can setup in desktop.
However, I do see you can set something similar up using tabular editor.
https://docs.tabulareditor.com/te3/tutorials/incremental-refresh/incremental-refresh-setup.html
I'm new to tabular editor and look forward to utilizing that tool going forward.
thanks again