DataSource Error

[OutofSpec]

Some odd reason, I started to get this error.  Can anyone help?

• OLE DB or ODBC error: [DataSource.Error] Dynamics365BusinessCentral: Request failed: The remote server returned an error: (400) Bad Request. ('Blanket_x0020_Order' is not an option. The existing options are: Quote,Order,Invoice,Credit Memo,Blanket Order,Return Order CorrelationId: d5cfad28-24b0-41fe-abfe-b0b372746847.).

[Joeshipday]

Any update on this issue as I think I'm getting the same:

[DataSource.Error] Dynamics365BusinessCentral: Request failed: The remote server returned an error: (400) Bad Request. ('Blanket_x0020_Order' is not an option. The existing options are: Quote,Order,Invoice,Credit Memo,Blanket Order,Return Order CorrelationId:...)

I'm using the built-in Power BI Business Central connector to connect to an Advanced BC AL API that I wrote. The API is a simple GET for the salesheader table. I was only able to get this error message when I tried to "load more" in the Power Query filter list for Document Type (or other fields). 

[lbendlin]

Have you tried without escaping the space, or is that something the connector does itself (inconsistently, apparently)?

[SaiTejaTalasila]

Hi @OutofSpec ,

If you are getting the error in existing report which is working earlier.You can open transform data and check your applied steps of your table one by one.

Thanks,

Sai Teja 

[lbendlin]

Are you using an OData connector or a different type of connector?  Try without escaping the space.

[OutofSpec]

I am using an OData connector.

Now the odd thing is that I only get this error on Thursdays.

[lbendlin]

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

[Joeshipday]

Thanks you for responding, I should have made that clear, no tranformation has been done to the API, this is the most basic config possible. 

All I did was select the API and load data. 

The preview data will load but refreshing the whole table fails. The errors I get from the general refresh are more generic so it was by luck that I found this more detailed error that at least points at how its failing, I'm just not sure why or where this is happening.

[lbendlin]

Guess you found a bug in the connector.  Curious to see that "Return Order"  doesn't (yet) raise the same error.

[Joeshipday]

I believe I have resolved this issue for my Custom API. 

Based on a Tip in this document: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-develop-cu...

I have added the following to my API header: ODataKeyFields = SystemId;

I did this in order to test the API in Power Automate as the response can be inspected in its raw format before the BI connector does its thing. 

This is no longer an issue for this API. I know this might not be helpful in situations where standard APIs are being used but it might point at the cause at least.

Sadly my original issue still remains so I'll have to continue to investigate that. 

[Joeshipday]

For anyone who might need it, I identified what was causing my original issue of generally non-descript failures in the Dataflow and "An existing connection was forcibly closed by the remote host" in Power BI Desktop when trying to query a business central API for the Sales Headers table (Sales Quotes, Sales Blank Orders, Sales Orders, Sales Return Orders, etc). 

On the BC Sales Header table there is a field Work Description that comes into BI as type Binary. It is a text stream (multi-line text) that appears to cause some issues when being consumbed in Power BI.

Removing this field/column from the Power query was enough to have it work normally.