Timeout period elapsed on OData Feed

[JohnR82]

Hi guys, 

On scheduling refresh of OData - edit credentials fails for one of my data entities - pulling from D365 FO,

I have seen similar messages where users have cross-company = true - this is also the same in this case but other data entities in the same report also have this and update credentials ok.

I have also updated the timeout in advanced editor and sought to optimise the dataset being published.

This report refreshes in Desktop but will not allow us to schedule refreshes online to allow end users to self serve. 

Any help on next steps would be greatly appreciated.

[Greg_Deckler]

You could check the Issues forum here:

https://community.powerbi.com/t5/Issues/idb-p/Issues

And if it is not there, then you could post it.

If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".

[Alarik]

Hi all,

we've got the same issue with timeout in PBI Service when connecting to Odata source. We found a solution using standart PBI and Odata tools. We use Odata to get data from our local accounting system, but maybe this solution could also fit D365.

What we do - we transform Odata into json and use Web connector in Power Query, not Odata:

1. Click on Get data and choose Web

2. Paste Odata url and add new parameter in the end of url   &$format=json

3. Provide credentials 

4. Convert into table

5. Click on List

6. Convert the list into table

7. Expand the columns

8. Note that all data from json is of text type, so you need to change it to appropriate.

The last thing I want to mention is that refreshing works fine only via personal gateway but  I hope that it is our local issue.