Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Grow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.

Reply
Anonymous
Not applicable

Actualización de Consultas de Manera Independiente

Hola

 

He hecho un origen de datos desde una carpeta para que la base de datos consolidada se actualice a medida que voy ingresando archivos con información nueva. Sin embargo, al actualizar la información el refresca todos los archivos nuevamente y quisiera saber si es posible que al actualizar los datos que estan en archivos independientes solo actualice los nuevos que se deben cargar.

 

Gracias!

1 ACCEPTED SOLUTION
BA_Pete
Super User
Super User

Hi @Anonymous ,

 

There's no way you can only update queries with new data within a Power BI report. Power Query works as follows:

Wipe all data > Import new data from all sources > Perform transformations > Send to data model.

There's no 'new data' detection. As such, the only way you could quickly and easily partition your data would be to set up all the queries that shouldn't refresh when new files are added (e.g. dimension tables, tables from sources that aren't subject to manual file updates etc.) in Dataflows, and give them their own refresh schedule.

This would mean that any sources that ARE reliant on manual file updates would need to be kept in the report, and would ALL refresh when a new file was added, but you could at least shield a number of other sources from this behaviour, potentially reducing refresh time and processing load.

 

Pete



Now accepting Kudos! If my post helped you, why not give it a thumbs-up?

Proud to be a Datanaut!




View solution in original post

1 REPLY 1
BA_Pete
Super User
Super User

Hi @Anonymous ,

 

There's no way you can only update queries with new data within a Power BI report. Power Query works as follows:

Wipe all data > Import new data from all sources > Perform transformations > Send to data model.

There's no 'new data' detection. As such, the only way you could quickly and easily partition your data would be to set up all the queries that shouldn't refresh when new files are added (e.g. dimension tables, tables from sources that aren't subject to manual file updates etc.) in Dataflows, and give them their own refresh schedule.

This would mean that any sources that ARE reliant on manual file updates would need to be kept in the report, and would ALL refresh when a new file was added, but you could at least shield a number of other sources from this behaviour, potentially reducing refresh time and processing load.

 

Pete



Now accepting Kudos! If my post helped you, why not give it a thumbs-up?

Proud to be a Datanaut!




Helpful resources

Announcements
Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.

Top Solution Authors
Top Kudoed Authors