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

We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now

Reply
vdburg
Resolver I
Resolver I

Parameters not showing up in the Power BI Service for incremental refresh

Hi,

I have been using Incremental Refresh for years. Now, suddenly when configuring a new report it doesn't show up in the Power BI service. It keeps saying that the parameters are still not defined in power query. 

I have configured the parameter RangeStart and RangeEnd, both as DateTime, on a datetime column. Then In the model view enabled Incremental refresh, keeping the last 10 years and updating the last 1 year. Published several times. It doesn´t appear.

Maybe I am missing something or something changed recently?

 

Best regards,

1 ACCEPTED SOLUTION

Yes. I understood. I'm saying it's ok not seeing the incremental refresh parameters. I have checked in an old report and I don't have them at Service. If it let you run a refresh after publishing everything activated, it should be working. You can validate the partitions with dedicated or ppu capacity to make sure it's there.

Regards


If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Happy to help!

LaDataWeb Blog

View solution in original post

8 REPLIES 8
vdburg
Resolver I
Resolver I

Thank you both @MasonMA and @ibarrau for taking the time to look at your end. I guess they depreciated it and should work somehow with the defined parameters in desktop

MasonMA
Super User
Super User

Can you share M query just for the relevant table? 

Hi @MasonMA,

 

let
Origen = Sql.Database("UNIPRBISQL01\UNIPRBISQL01", "dwh_unicef"),
dbo_FACT_COMPROMISO = Origen{[Schema="dbo",Item="FACT_COMPROMISO"]}[Data],
#"Otras columnas quitadas" = Table.SelectColumns(dbo_FACT_COMPROMISO,{"ID_COMPROMISO", "FEC_ALTA", "FEC_MODIF_REGISTRO"}),
#"Filas filtradas" = Table.SelectRows(#"Otras columnas quitadas", each [FEC_MODIF_REGISTRO] >= RangeStart and [FEC_MODIF_REGISTRO] < RangeEnd),
#"Filas ordenadas" = Table.Sort(#"Filas filtradas",{{"FEC_MODIF_REGISTRO", Order.Ascending}})
in
#"Filas ordenadas"

Your queries are actually structured correctly for Incremental Refresh. 

Thanks to @ibarrau . I validated from my end and it's true they no longer appear in Service. 

vdburg
Resolver I
Resolver I

Hi,

I am adding more examples: This is what I do have for older reports in the power BI service:

 

vdburg_0-1772628946470.png

Now, I configure the same way I get this:

 

vdburg_1-1772629007954.png

 

Yes. I understood. I'm saying it's ok not seeing the incremental refresh parameters. I have checked in an old report and I don't have them at Service. If it let you run a refresh after publishing everything activated, it should be working. You can validate the partitions with dedicated or ppu capacity to make sure it's there.

Regards


If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Happy to help!

LaDataWeb Blog

Hi @ibarrau,

We only have pro licenses, so It´s my understanding that I am unable to connect to a xmla endpoint.

I thought maybe you don´t have to define the parameters again in the service, and that by defining them in Power BI desktop it should work, but I tried to see what happens if I just define to update the last 3 days, but it takes too long. So I don´t think it´s working.

 

Best regards

 

ibarrau
Super User
Super User

Hi. I'm not sure what the problem is here. When you configure regular parameters you will see them in the semantic model settings. However, when creating RangeStart and RangeEnd as datetime configuring incremental refresh, I don't remember seeing those for a long time in PowerBi Service. That's how you know it has worked in pro, because they are not there. After configuring and sending to service, just refresh to make sure it works. 
If it's a dedicated capacity workspace you can validate it connecting from SQL Manangement studio to the xmla endpoint to check partitions.

I hope that helps,


If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Happy to help!

LaDataWeb Blog

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.