Scheduling refresh with Web as datasource

[Anonymous]

Hi,

I have an issue regarding the schedule refresh for the online services.

My dataset is working fine where I use "Web" as datasource and fetching data from an API with a Bearer token provided in the header.

When refreshing the dataset on desktop everything works fine, no issues at all, I can get all the data I want.

The dataset can be published to online services without any problems aswell, all the data is preloaded with the dataset from when I refreshed the pbix file.

Then here is my issue where I try to set up a scheduled refresh, the warning triangel appears saying;

"Data source errorScheduled refresh is disabled because at least one data source is missing credentials. To start the refresh again, go to this dataset's settings page and enter credentials for all data sources. Then reactivate scheduled refresh."

And when I enter the settings of the dataset the Gateway connection says;
"You don't need a gateway for this dataset, because all of its data sources are in the cloud, but you can use a gateway for enhanced control over how you connect"

And under Data source credentials it says;

"Your data source can't be refreshed because the credentials are invalid. Please update your credentials and try again."

Though I dont use or have any Web credentials it is requiring this from me, all I Authorize with is a Bearer token which is passed by in the header.

Any suggestion why online services is behaving this way or any solution so that I can add a scheduled refresh to this datasource?

All help is appreciated.

[v-xuding-msft]

Hi @Anonymous ,

I think you could use RelativePath option parameter to have a try.  Please Reference:

https://community.powerbi.com/t5/Service/Refresh-not-working-in-Power-BI-Service/td-p/674167

Best Regards,

Xue Ding

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

[Anonymous]

Hi @v-xuding-msft ,

Thanks for response, unfortunately this did not work either, as the thread starter from the link you provided did not solve it either with that example, eventhough it is accepted as a solution..

Any other workarounds or is this a common bug in power bi?

I have been consulting with developers at my company who work daily with cloud solutions, their spontaneous idea is that the problem lies with power bi not passing by the header when publishing to online services, skipping the token authentication alltogether.

My problem persists, any help is appreciated.