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

Power BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.

Reply
mribeiro
New Member

Incrementally load new data without processing all dataset

Hi guys,

 

I'm with a problem to update "new" data to a table with incremental refresh configuration.

 

Follow bellow a summary of the model.

mribeiro_1-1643978522568.png

 


I have a referense table conected to others, where I have the the App Keys and Secrets of my clients (The tables dProjects and fSales come from a web datasource).

 

When I add a new client, in the next scheduled refresh on Power BI Service, automatically the tables will update with this new data. But, the problem is with fSales. How the incremental refresh is configurated, the data from this new client don't will be loaded in the past.

 

Of course, I can force the update using Tabular Editor or SSMS, but I don't want to update all my dataset fSales, because I have to many clients and it can take to many hours.

 

So, I would like to run a refresh script with a where contitional in a column (Refresh where dCllients[Client] = "New client"), is this possible? Or what's the best solution in this case?

 

 

Thanks in advance.

 

3 REPLIES 3
collinq
Super User
Super User

HI @mribeiro ,

 

As I am sure you know, the incremental refresh is using a date column to determine the "incremental" data to refresh and it is looking for changes in data since that date.  Based on that date parameter the system will not go back in time to find previous sales transactions for that specific client since that would be "archived data" already and not picked up.

If I understand your description this is exactly what is happening.

I don't think that there is a particularly easy programmatic way to get around this issue.  If this is something that happens infrequently the way I would do this is to create a new query - similar to yours - where you go and JUST get the new client data, then, I would append this to the master sales table and that way you have the historical data available to you and going forward the new client is picked up with the incremental refresh.

Let me know your thoughts.




Did I answer your question? Mark my post as a solution!

Proud to be a Datanaut!
Private message me for consulting or training needs.




Hello @collinq ,

 

Thanks for your reply!

 

Exactly.. you got the issue.

 

You had a great idea. I followed your suggestion, but unffortunelly I came cross other issue: It's not possible append data in a already incremental configurated table. It's simillar of this issue: https://community.powerbi.com/t5/Service/Incremental-refresh-from-Azure-DataLake/m-p/559711#M56914

 

You have some suggestion to get around this new issue?

 

Thanks.

 

 

HI @mribeiro ,

 

Hmmmmmm, ok, perhaps you could do part (or all) of this in a DataFlow?  You could have the "old" stuff in the dataflow and not necessarily refresh it every day?  OR, you could do the new stuff in the dataflow?  Either way, if half the work is done in a dataflow and then you just combine the data together in the final report I think that should work.  




Did I answer your question? Mark my post as a solution!

Proud to be a Datanaut!
Private message me for consulting or training needs.




Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.