Save past totals, connect to Azure DevOps

[Syndicate_Admin]

I have the following table of bugs per team, where each column is a measure, with data that I bring from Azure DevOps.

I need to be able to save the totals, so when I do a new refresh I can contrast it with the previous one (I only need the last one).

Any ideas for not doing it manually in an excel? The ideal would be to be able to choose which one to keep, since although the refresh is scheduled to be done every day, only what is of interest is for a specific day.

[v-nmadadi-msft]

Hi @Syndicate_Admin,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the community members for the issue worked. If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Thanks and regards

[v-nmadadi-msft]

Hi @Syndicate_Admin,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If our responses has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-nmadadi-msft]

Hi @Syndicate_Admin,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-nmadadi-msft · Accepted solution]

Hi @Syndicate_Admin ,
Thanks for reaching out to the Microsoft fabric community forum.

Snapshots are not possible natively in Power BI, but we can work around that limitation using Power Automate. Power Automate allows you to schedule and capture data at specific intervals, creating a snapshot of the report or dataset. 

Another approach is to use Dataflow Gen 2 to store and track historical totals in Power BI without manual exports. By creating a Power BI Dataflow or a Microsoft Fabric Lakehouse, you can efficiently centralize and manage the data. The dataflow can output bug data to the Lakehouse, where you can store snapshots with corresponding dates, enabling seamless comparisons over time. This method ensures accurate historical tracking while automating data storage and reducing manual effort.

If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thanks and Regards