Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
We have several PBI models that use incremental refresh. We are very familiar with the process and are enjoying the benefits. However the July 2020 PBI Desktop is causing us problems. We can create a new & simple model with single fact table (imported). Prior to defining RangeStart and RangeEnd we can publish this model and setup normal refresh via the gateway. However when we add RangeStart and RangeEnd to the model it appears PBID converts our fact table from "import" to "direct connect". When we publish this model and go to check the refresh settings in PBI we no longer see the "Scheduled Refresh" option. Instead we see "Schedule Cache Refresh". If we instead use an older version of PBID we are able to define incremental refresh as normal. Hoping someone can confirm this issue...
Hi @bpearce ,
Sorry for that, We cannot reproduce the issue here and also not found an effective solution.
We suggest you to open a ticket here for help: https://powerbi.microsoft.com/en-us/support/
According to your description, it may be a version problem.
Best regards,
Community Support Team _ zhenbw
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
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.
| User | Count |
|---|---|
| 46 | |
| 43 | |
| 39 | |
| 19 | |
| 15 |
| User | Count |
|---|---|
| 68 | |
| 67 | |
| 31 | |
| 27 | |
| 24 |