This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
I have a power Query set up which pulls data from Sharepoint List. I do my transformations there and end up with 4 rows, one of which is a column I created, today's date.
This loads to Excel.
How can I set it up so instead of replacing records it appends to a table which I pulled few days before.
I want to end up with a table which has something like
| Snapshot Date | Application ID |
| 20/4/2025 | ABC |
| 20/4/2025 | BCD |
| 22/4/2025 | ABC |
| 22/4/2025 | BCD |
| 26/4/2025 | ABC |
| 26/4/2025 | BCD |
Solved! Go to Solution.
Imagine the weekly update is like in the blue table (screenshot below) and the combined one from earlier updates is the green one and comes from an earlier run of the query
The following M-code will connect to tblSource (Source) AND tblPQ (History) and then append Source to History to create an extended tblPQ.
let
Source = Excel.CurrentWorkbook(){[Name="tblSource"]}[Content],
History = Excel.CurrentWorkbook(){[Name="tblPQ"]}[Content],
#"Appended Query" = Table.Combine({History, Source}),
#"Changed Type" = Table.TransformColumnTypes(#"Appended Query",{{"Snap", type date}, {"ID", type text}})
in
#"Changed Type"It results in this:
and a next run may look like this:
etc.
@some_analyst To implement this you need to either keep all historical data in different folder/files with names that can help in identifying next set of rows or you need to keep appending new data everyday.
If you replace the file everyday then PQ can't get the data that is gone.
Hi @some_analyst ,
Has your issue been resolved? If a community member's response addressed your query, please consider marking it as Accepted Answer and click Yes if you found it helpful.
If you have any further questions, feel free to reach out.
Thank you for being a valued member of the Microsoft Fabric Community Forum!
Hi @some_analyst ,
We haven’t heard back from you regarding our previous response and wanted to check if your issue has been resolved.
If it has, please consider clicking “Accept Answer” and “Yes” if you found the response helpful.
If you still have any questions or need further assistance, feel free to let us know — we're happy to help!
Thank you!
Hi @some_analyst ,
Has your issue been resolved? If a community member's response addressed your query, please consider marking it as Accepted Answer and click Yes if you found it helpful.
If you have any further questions, feel free to reach out.
Thank you for being a valued member of the Microsoft Fabric Community Forum!
Imagine the weekly update is like in the blue table (screenshot below) and the combined one from earlier updates is the green one and comes from an earlier run of the query
The following M-code will connect to tblSource (Source) AND tblPQ (History) and then append Source to History to create an extended tblPQ.
let
Source = Excel.CurrentWorkbook(){[Name="tblSource"]}[Content],
History = Excel.CurrentWorkbook(){[Name="tblPQ"]}[Content],
#"Appended Query" = Table.Combine({History, Source}),
#"Changed Type" = Table.TransformColumnTypes(#"Appended Query",{{"Snap", type date}, {"ID", type text}})
in
#"Changed Type"It results in this:
and a next run may look like this:
etc.
The only way to acheive that in Power Query and to keep the data, is to created a new table for each refresh
But if you need to update a table or if someone refresh the table, you will lose all snapshots
My suggestion is to built something like this, would be to use Fabric or you can also do that with Power Automate and dataverse
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.