Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago

refresh data from excel sharepoint with on-primes data gateway

hi all,

I  have a dataset that connect to different kinds of data source: SQL server, sharepoint worksheets.

 

I set up a auto refresh schedule that trigger once a week, each time I complete update data on my SQL server tables.

 

It work perfectly fine with the SQL tables (sometime slowly refresh but i still get the updated data). But when my team modify the

Sharepoint worksheets, the refresh still finish without any error notification, but no new data was updated to my dataset (still the old data before refresh). 

 

I tried serveral time but nothing change, the PBI service doesn't show any error, so I can not figured out what is wrong with my file or my setup.

 

Anyone who solved this please show me how to fix it?

Thank you and have a great work every day!

 

thanhnt

3 Replies

  • christinepayton's avatar
    christinepayton
    Icon for Most Valuable Professional rankMost Valuable Professional

    If you refresh it in the desktop, does it update?

     

    If it works in the desktop, but not cloud, it indicates that there's something up with the datasource credentials that are stored for SharePoint or with data privacy settings. If it doesn't work in either one, then there's an issue with the query (e.g. people renaming sheets that break the query reference, though this will usually give an error). 

  • Anonymous's avatar
    Anonymous
    Not applicable

    It does work on desktop.

    All I have to do is download the latest version of dataset --> hit refresh locally on my PC --> upload the dataset again. That whole thing sometime takes me 20-30mins of manual working.

    And because of the update on sharepoint worksheet is serveral time on some day so It's really painful doing those manual stuff.

    • christinepayton's avatar
      christinepayton
      Icon for Most Valuable Professional rankMost Valuable Professional

      Yeah I would re-enter the credentials in the datasource settings in the cloud, potentially check your datasource privacy settings and make sure they are all set (usually "organizational") and republish. Those things will usually give you an error message, though, so not sure why it would just not be present...