Failed to update data source credentials

OleksiyPro

I notice that there is an existing issue already reported internally: CRI 29226258

I’ll keep an eye on it and post here once there is any update about it.

Best Regards,

Herbert

This issue exists since end of November 2016. Most already existing reports work. All new published reports show this issue with 3 ODATA sources instead of one and the "fail to update credentials". 

This was also already reprduced in the internal PowerBI and Project Online Testtenant, at least at the German Power BI Support. 

Its beyond my understanding why such an issue which impacts ALL ProjectOnline User which use PowerBI needs so long to fix and why this major issue is not listed on the support side as known issue with daily updates what the status is

Hi All,

I’ve got some info about the fix date, it will be expected on 2/1/2017.

Best Regards,

Herbert

Hi Guys,

Is this issue resolved? Today i tried publishing a project line data set from power bi desktop to online, it got published sucessfully. But when i tried to schedule a data refresh, it throwed me the same error as mentioned in this post. Please let me know if there is any resolution steps to solve this issue.

Thanks in advance.

Regards,

Sivapratap.

Hello,

Is there an update to this issue yet? The issue still exists so I assume the fix wasn't deployed 1st Feb? 

Thanks

Paul

Hi Paul,

I believe microsoft is yet to find solution for this issue. But there are few workarounds where we might not end up with this issue.

I tried connecting to  project online OData Feed with respective to each table seperately like Projects,Tasks etc and did merge query and column selection etc. When i published the same to Power BI Online , and scheduled refresh, it happens successfully.

Now , i am trying to merge data from Sharepoint Online and Project Online and try a schedule refresh. Hope the above said can be treated as a workaround till microsoft shows up with a resolution.

Hope this helps.

Thank You,

Sivapratap.

Hi Sivapratap,
 

I think the issue for me is that the query URL contains [] so that the Project Online OData API is localised. I did a quick test the other day and can repro the issue in a simple report with [en-US] in the URL. Took a copy of that report file and removed the [] part of the URL and that worked fine. Would be good to know / have an indication when this issue will be resolved?
 

Paul

Hi Paul,

Thanks for the workaround you shared. it really helped a lot to narrow down on issue. Hope, microsoft will take in their feb release.

Regards,

Sivapratap