Failed to retrieve dynamic outputs, Business central powerautomate flow error

(0) Share

Report

Posted on by mheinst

We have a powerautomate flow with item information from Business central.

I think after een update from BC we are getting this error. And the flow stopped working.

Failed to retrieve dynamic outputs. As a result, this operation's outputs might not be visible in subsequent actions. Error details: The dynamic operation request to API 'dynamicssmbsaas' operation 'GetTableV2' failed with status code 'InternalServerError'. Error response: { "error": { "code": 500, "source": "europe-001.azure-apim.net", "clientRequestId": "bef1c0ee-913d-49e0-bc5c-35de9dae2039", "message": "BadGateway", "innerError": { "status": 500, "message": "Unexpected end when reading JSON. Path 'properties[17]', line 1, position 1637.\r\nclientRequestId: bef1c0ee-913d-49e0-bc5c-35de9dae2039", "error": { "message": "Unexpected end when reading JSON. Path 'properties[17]', line 1, position 1637." }, "source": "dynamicssmbsaas-ne.azconn-ne-002.p.azurewebsites.net" } } }

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (0)

PhilS 9 on at

Like (0)

Report

Did you get anywhere with this, we have a similar error, but only for a particular table in BC and using the V3 version of GetTable..

The dynamic operation request to API 'dynamicssmbsaas' operation 'GetTableV3' failed with status code 'InternalServerError'. Error response: { "error": { "code": 500, "source": "europe-002.azure-apim.net", "clientRequestId": "aea1261a-857d-4ef0-b004-0d9e59310bc7", "message": "BadGateway", "innerError": { "status": 500, "message": "Unexpected end when reading JSON. Path 'properties[43]', line 1, position 7500. clientRequestId: aea1261a-857d-4ef0-b004-0d9e59310bc7", "error": { "message": "Unexpected end when reading JSON. Path 'properties[43]', line 1, position 7500." }, "source": "dynamicssmbsaas-we.azconn-we-002.p.azurewebsites.net" } } }

Was this reply helpful? Yes No
Paul_Taylor 2 on at

Like (0)

Report

Bump. I'm having the same issue.

Was this reply helpful? Yes No
Karokaro 13 on at

Like (0)

Report

Any news?

Was this reply helpful? Yes No
PhilS 9 on at

Like (0)

Report

Our issues are now resolved, they suddenly started to work.

Apparently nothing was done by us, D365 side, or the BC partner...

The issue would appear to be with the definition of the API and synchronising those changes between BC and D365, so that they are in synch. Thankfully we've got a few instances so we can check between the development, UAT and Prod instances and variations between them. I would talk to the BC partner to ensure nothing has changed on their side or see if a new API endpoint could be made available in a non-production instance.

Was this reply helpful? Yes No