Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
I have a table that shows for each team, how many bugs are not assigned to a sprint, assigned to a sprint that already passed, are on hold, and other measures...
In order to get the numbers, we pull data from Azure DevOps with scheduled refresh twice a week.
I would like to save the totals, so every time we do a new refresh, we can compare with last time.
Any thoughts?
Hi @florencialuna ,
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.
Hi @florencialuna ,
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 the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @florencialuna ,
I hope the provided information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you
The good option to to pull the data into a database or warehouse before pulling into Power BI to keep a history.
A hacky way would be with incremental refresh. You could include RangeStart and RangeEnd to effectively do nothing, but are required to active the policy. Create a refeshDate column in powerquery set to today(). You would set the active window to a day and archived for whatever period you want keep. On refresh you'd get your new data in the active partition with the date of export. This would then rolling to the archive window the following day. You will need to bootstrap by first publishing to the service, then use tabular editor to apply the policy. Then can refresh as normal, this is to avoid filling the archive partition. Side note, if the schema of the table ever changes you may lose your partitions, depending on what you change. Realtically should go for option 1
Any suggestions for choosing the database or warehouse?
Hi @florencialuna ,
Thanks for reaching out to the Microsoft fabric community forum.
Save Trace Results to a Table - SQL Server Profiler | Microsoft Learn
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Best Regards,
Menaka.
Community Support Team.
User | Count |
---|---|
84 | |
73 | |
67 | |
42 | |
35 |
User | Count |
---|---|
109 | |
56 | |
52 | |
45 | |
43 |