Forum Discussion
Lakehouse with cut off date
Hi Felpan ,
Yes, To achieve this, you can utilize Dataflows Gen2 in Microsoft Fabric to ingest each budget version separately, assign timestamps to track updates, and store the data in a Lakehouse.
1. Set up Dataflows Gen2 to connect to your Excel files in SharePoint and import new data monthly.
2. In Power Query, add a column to label each file with a cut off date, such as 1Sep or 1Oct, for version tracking.
3. Load the data into a Lakehouse using the append option to store each month's version without overwriting previous ones.
4. Use Power BI to easily analyze and compare budget changes over time.
For a more detailed explanation, please review the official Microsoft documentation linked Below
Create your first Microsoft Fabric dataflow - Microsoft Fabric | Microsoft Learn
Helpful Reference:
Copy sample data into Lakehouse and transform with dataflow - Microsoft Fabric | Microsoft Learn
Yugandhar
CST Member.
So how would this look like? ingest each budget version separately while assigning timestamps to track updates
Community SupportHi Felpan ,
Yes, To achieve this, you can utilize Dataflows Gen2 in Microsoft Fabric to ingest each budget version separately, assign timestamps to track updates, and store the data in a Lakehouse.
1. Set up Dataflows Gen2 to connect to your Excel files in SharePoint and import new data monthly.
2. In Power Query, add a column to label each file with a cut off date, such as 1Sep or 1Oct, for version tracking.
3. Load the data into a Lakehouse using the append option to store each month's version without overwriting previous ones.
4. Use Power BI to easily analyze and compare budget changes over time.
For a more detailed explanation, please review the official Microsoft documentation linked Below
Create your first Microsoft Fabric dataflow - Microsoft Fabric | Microsoft Learn
Helpful Reference:
Copy sample data into Lakehouse and transform with dataflow - Microsoft Fabric | Microsoft Learn
Yugandhar
CST Member.