Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Hi everyone. I was able to set up several of our Power BI reports to use an incremental refresh policy on certain large tables. Everything is Import, not Direct Query. So far it's working great and as expected. Over time though, the older data will gradually change, and we need a way to schedule or trigger a FULL refresh (i.e. all partitions) maybe once a week or so. Can someone advise how to do this? We primarily use Power Automate to trigger refreshes, but none of the tasks have that option. What's the best approach here? Thanks.
Solved! Go to Solution.
Hello you can select wich partition to refresh with SSSM. Maybe also with other tabular editor or via api. Try to look at this documentation https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-xmla
Of course I don't know if you can do it with a PRO sub.
Because I read:
For models in a workspace assigned to a Premium capacity, partitions can be managed through the XMLA endpoint by using tools like SQL Server Management Studio (SSMS), the open-source Tabular Editor, scripted with Tabular Model Scripting Language (TMSL), and programmatically with the Tabular Object Model (TOM).
Also:
SQL Server Management Studio (SSMS) can be used to view and manage partitions created by the application of incremental refresh policies. By using SSMS you can, for example, refresh a specific historical partition not in the incremental refresh period to perform a back-dated update without having to refresh all historical data. SSMS can also be used when bootstrapping to load historical data for large models by incrementally adding/refreshing historical partitions in batches.
Specify the refresh type as full instead of automatic
cube - SSAS Tabular Model - Partition Refresh and Schedule - Stack Overflow
Hello you can select wich partition to refresh with SSSM. Maybe also with other tabular editor or via api. Try to look at this documentation https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-xmla
Of course I don't know if you can do it with a PRO sub.
Because I read:
For models in a workspace assigned to a Premium capacity, partitions can be managed through the XMLA endpoint by using tools like SQL Server Management Studio (SSMS), the open-source Tabular Editor, scripted with Tabular Model Scripting Language (TMSL), and programmatically with the Tabular Object Model (TOM).
Also:
SQL Server Management Studio (SSMS) can be used to view and manage partitions created by the application of incremental refresh policies. By using SSMS you can, for example, refresh a specific historical partition not in the incremental refresh period to perform a back-dated update without having to refresh all historical data. SSMS can also be used when bootstrapping to load historical data for large models by incrementally adding/refreshing historical partitions in batches.
Hi @bvy ,
If you have Premium, Premium Per User, or Power BI Embedded, you can do a full refresh/history partition refresh by enabling XMLA Endpoint for the workspace and then connecting to the workspace via the tool (ssms, tabular editor ...).
You can refer to Gabry's and lbendlin's methods.
If you are familiar with the PBI rest api, you can also use it to implement enhanced refresh. This also requires Premium, Premium Per User, or Power BI Embedded.
Enhanced refresh with the Power BI REST API - Power BI | Microsoft Learn
Best Regards,
Gao
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
How to get your questions answered quickly -- How to provide sample data in the Power BI Forum
User | Count |
---|---|
120 | |
69 | |
68 | |
57 | |
50 |
User | Count |
---|---|
166 | |
82 | |
68 | |
65 | |
54 |