Difference in azure portal and VS code for the dataverse connector

Jonas Karlsson 6 Reputation points
2024-05-02T14:03:18.9433333+00:00

Having issues using VS code with the Dataverse connector and when I'm using the Bound to Action method.

In Azure Portal it seems to work fine, but when using VS code I suddenly get additional required parameters that are mandatory. I need to manually remove the parameters from the json every time I use the designer. The workflow runs when I publish and the parameters has been removed, if I just fill in any value in the parameters and publish the workflow, it fails on every run.

It has nothing to do with the input to the action in Dynamics, the required parameters shows up on every action.

Anyone know a workaround in VSCode?

Azure Portal
5

body of the request in vscode.

 "body": {
                                "error": {
                                    "code": "",
                                    "message": ""
                                }
                            }

VSCode
4

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,378 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Ryan Hill 26,156 Reputation points Microsoft Employee
    2024-05-04T00:04:45.6466667+00:00

    Hi @Jonas Karlsson,

    Thank for your taking the time to post your question on the Q&A Platform. This issue seems more related to either the VS Code IDE or the Azure Logic App extension. Unfortunately, those experts don't actively monitor Microsoft Q&A forum.

    What I would suggest is reporting the problem within VS Code. That mechanism should be able to capture more telemetry that can lead to the direct cause of your issue. You can also create a new issue for VS Code. Unfortunately, creating a new issue for the Azure Logic App Extension is currently archived.

    0 comments No comments