Updating existing refresh policy

[Anonymous]

Hi all,

I’m working with a dataset in Microsoft Fabric and wanted to know if it’s possible to update an existing refresh policy (e.g., rolling window or incremental period) programmatically—either via the XMLA endpoint, TMSL, or any API.

Is this currently supported in Microsoft Fabric or Power BI Premium? If yes, any pointers to documentation or examples would be greatly appreciated.

Thanks!

[Anonymous]

Hi @Anonymous,

Thanks @pallavi_r  and @lbendlin for Addressing the issue.

we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Regards,
Vinay Pabbu

[Anonymous]

Hi @Anonymous,

May I ask if you have gotten this issue resolved?

If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

Regards,
Vinay Pabbu

[Anonymous]

Hi @nilaratan,

we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Regards,
Vinay Pabbu

[pallavi_r · Accepted solution]

Hi @Anonymous ,

Please see if below links meets your requirement.

1. Enable power bi project to include tmdl

https://www.kevinrchant.com/2024/02/23/upgrading-an-existing-power-bi-project-to-include-tmdl-file-format/

2. Set up git integration

3.Modifiying refresh policy in the file

https://docs.tabulareditor.com/te3/tutorials/incremental-refresh/incremental-refresh-setup.html

https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-xmla#adding-an-incremental-refresh-policy-and-real-time-data-programmatically

4.Trigger refresh using cli or rest api

5.And then polling to check the status of refresh till it is completed or failed.

Thanks,

Pallavi

[lbendlin]

Schedules are limited to 48 slots per day, with the weekdays selectable.

You can completely ignore that and set up your own refresh process via the REST API calls.

You MUST be aware that refreshes are asynchronous, so you MUST implement your own refresh status polling.

Ideally you only refresh your semantic model when its datasources have actually changed.  Ideally you get notified about that by the data sources.