Failed to update data source credentials:

[Anonymous]

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

[Anonymous]

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! 

[Anonymous]

Sorry, I gave up and found another solution without odata 

[Anonymous]

Thank you so much for the reply!

I can see that it is probably we will have to move on from OData as well. 

[GilbertQ]

Hi 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?

[Anonymous]

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.

[GilbertQ]

Hi 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.

[Anonymous]

Hi Gilbert

Still not sure thats the problem.

The message say credentials og not timeout in Load.

When I look at the credentials overview it says that there are problems with this table, and not any of the other tabels. And when I try to type in the credentials I get the message.

[GilbertQ]

The errors can be hard to read, but it definitely says "Timeout expired. The timeout period elapsed prior to completion of the operation"

Which indicates a timeout issue.

[Anonymous]

Correct you are. But it's not when I try to update da datamodel, but when I try to update my credentials to one of the tabels.

[GilbertQ]

Is there any way to try and get it to work in similar way as the other tables?

[Anonymous]

All tables come from the same source and use the same credentials.


The only difference are the that I build the m query string myself on this table to exclude some columns before loading the table

[GilbertQ]

It would appear that it is then doing some query folding when not using the M Steps.

Possibly see which step is causing it to not fold the query back?

[Anonymous]

I'm not sure of what you mean with your last post?

[GilbertQ]

Hi there,

What I meant was, with query folding it allows the query to be run on the source system and not in the Query Editor