Forum Discussion
Failed to update data source credentials:
I have a report that with out problem update in desktop, but in online edition it wount accet credentials to one of the tabels.
Alle the tabels are Odata feed from the same NAV. The only differense one this table and the other tabels are that I have made the call with my own M statment so I should not load the entire table.
The last part of the M String are this one:
All the othe tabels, that are working both in desktop and online, are loaded total, and not with ?$select=...........
---------------------------------------------------------
Failed to update data source credentials: Timeout expired. The timeout period elapsed prior to completion of the operation.Hide details
| Activity ID: | 87509aa1-b84d-41d1-b29b-c46944527abd |
| Request ID: | eebf65dc-415f-0bd6-bd1c-f4a8246473fd |
| Status code: | 400 |
| Time: | Tue Mar 26 2019 19:51:33 GMT+0100 (Centraleuropæisk normaltid) |
| Version: | 13.0.8885.144 |
| Cluster URI: | https://wabi-europe-north-b-redirect.analysis.windows.net |
14 Replies
- GilbertQSuper UserHi there
There is a known issue with the March edition of the On-Premise Data Gateway, so if possible to update it to the latest version and try and refresh again?- AnonymousNot applicable
Hi Gilbert
Thx for helping. But im afraid that i doesn't help. I use a Odata feed from NAV, and therefor don't use a Data Gateway.- GilbertQSuper UserHi there
It appears that this table is taking too long to get the data from NAV and is timing out
I would suggest looking to see if there are any ways to improve getting the data. When you are working on the Desktop there is no timeout happening as far as I am aware.
- AnonymousNot applicable
Hello Henrik,
I have the exact same structure (NAV db source via OData) and experiencing the same problem as this. Did you manage to solve it?
Thank you!
- AnonymousNot applicable
Sorry, I gave up and found another solution without odata
- AnonymousNot applicable
Thank you so much for the reply!
I can see that it is probably we will have to move on from OData as well.