Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe'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
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,
Solved! Go to 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
Happy to help!
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.
Hi,
I am adding more examples: This is what I do have for older reports in the power BI service:
Now, I configure the same way I get this:
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
Happy to help!
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
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,
Happy to help!
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 2 |
| User | Count |
|---|---|
| 8 | |
| 8 | |
| 6 | |
| 6 | |
| 5 |