DataEntity OData Call Returning 502 Bad Gateway Error in Application/Octet Format

(1) Share

Report

Posted on by Mahesh.0507

Hi all,

I'm currently facing an issue with my Logic App when attempting to insert records via OData calls to a Data Entity in Dynamics 365 for Finance and Operations (D365FO).It's throwing a status code 502 & the JSON response content is returned in application/octet-stream format.

Upon decoding, it was an HTML code of a 502 Bad Gateway error pop-up box.

I need to understand Why is the response content encoded & returned in application/octet-stream instead of a string [Bad Gateway]?

Is there a way to configure the response headers in the D365FO environment to ensure that errors are returned in a string/text format rather than application/octet-stream?

Thanks !

All responses (3)

Answers (0)

Martin Dráb 232,942 Most Valuable Professional on at

Like (0)

Report

DataEntity OData Call Returning 502 Bad Gateway Error in Application/Octet Format

Another alternative is the Dataverse connector (with F&O data entities as virtual entities).

Before trying to import anything, are you able to successfully list entities (/data/ endpoint)?
Mahesh.0507 32 on at

Like (0)

Report

DataEntity OData Call Returning 502 Bad Gateway Error in Application/Octet Format

Hi Martin Dráb !

Currently I'm not using any, this is a HTTP action. I've switched from F&O connectors to HTTP action OData calls due to rate limits.
Martin Dráb 232,942 Most Valuable Professional on at

Like (0)

Report

DataEntity OData Call Returning 502 Bad Gateway Error in Application/Octet Format

Which connector are you using in Logic Apps?

(Moved from Dynamics AX forum.)