Forum Discussion

_power_bi's avatar
_power_bi
Helper I
1 year ago
Solved

Incremental Refresh not working in Service

We have a Fabric datalake setup with a table there as a source in Power BI.  We also have an on-prem SQL Server as a source. I used the RangeStart and RangeEnd parameters  for incremental refresh on ...
Need Help
  • _power_bi's avatar
    _power_bi
    1 year ago

    I removed incremental refresh (right clicked on the table in the pbix and turned it off) and then saved a new pbix and published to my workspace.  It took about 20 minutes and refreshed. So, the issue is with the incremental refresh from a Fabric Lakehouse table. 

     

    I noticed that when turning on incremental refresh in desktop, there is warning that it is unable to confirm if the query can be folded. (The query was a select * but it was a native query).  I removed that and simply connected to the table then filtered to the paramaters as before.  If you right click on the applied step (not the source step but any steps after), it should say 'view native query'.  If it doesn't allow you to click that, then it probably is not "foldable".  Again, I am not sure why the error was credential related. That threw me off. 

v-achippa's avatar
v-achippa
Community Support
1 year ago

Hi _power_bi,

 

Thank you for reaching out to Microsoft Fabric Community.

 

Thank you lbendlin for the prompt response.

 

The error indicates an issue with the gateway credentials. Since the refresh works in desktop but fails in the service, please follow below steps:

  • In the service go to Settings --> Datasets --> Data Source Credentials and re-enter credentials for both Fabric Data Lake and on-prem SQL server and verify that all sources are correctly authenticated.
  • Ensure that the on-premises data gateway is updated to the latest version to prevent compatibility issues.
  • The column used for incremental refresh must be in datetime format (not string or other format).
  • In the service go to Refresh History and check if there are any additional error messages beyond the credentials issue.

After performing these steps, try refreshing again. If the issue persists and failure is after exactly 70 minutes, it’s a known issue and as Ibendlin said we have a ticket open for the issue.

 

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

 

Thanks and regards,

Anjan Kumar Chippa