Forum Discussion
Odata connection with filter in Gateway
I'm setting up some new Odata connections in the gateway. The first was created successfully, but the second gives an error. Upon investigation, some Odata connections that were working are now giving errors. The connection that I could not create included a filter (...?$filter=Order eq 'O'); if I remove the filter, the connection is successful. However, this connection requires the filter in order to return data.
The same url with the filter returns data without issue in Power BI Desktop.
Here is the error I am receiving when creating the connection:
Unable to connect: We encountered an error while trying to connect to . Details: "We could not register this data source for any gateway instances within this cluster. Please find more details below about specific errors for each gateway instance."
More details on the error:
| Underlying error code: | -2147467259 |
| Underlying error message: | Timeout expired. The timeout period elapsed prior to completion of the operation. |
| DM_ErrorDetailNameCode_UnderlyingHResult: | -2147467259 |
| Microsoft.Data.Mashup.HostingError.Reason: | Timeout |
Also of note, when I click the 'Troubleshoot connection problems' link, I get a 404 error.
2 Replies
Anonymous,
Currectly, OData filter are not supported in Power BI Service although it's working in Power BI Desktop.
The solution is to Filter from the Power Query editor that generate a call to the function Table.SelectRows: https://msdn.microsoft.com/en-us/library/mt260810.aspx.
Regards,
Lydia