Closed corredma closed 2 days ago
Taking a look at the swagger is showing the features parameter typed as an array. This is why the new designer is requiring the user to define an array value for that parameter. Old designer does not enforce type matching like new designer does. The issue seems to be located in the connector / backend somewhere, where even though the parameter is typed as an array, if an array is passed it seems to respond with an error.
Discussed with Milin and this does appear to be a backend issue. We saw no outgoing requests related to the actions from my repro, so something in the backend is catching this and returning the error we see in UX.
Duplicate of https://github.com/Azure/logicapps/issues/1202
Thanks a lot! I could not find the duplicate before and I create a new one but it helped a lot.
Thanks again, BR.
Describe the Bug with repro steps
So please, let us know how we can get KeyValuePairs working with new designer.
Or let us know if it is possible to use old designer and how to do it. In my team 2 of us have the new designer (without being able to change it to old one) and other 2 team members have the old designer.
Thanks,
BR.
What type of Logic App Is this happening in?
Consumption (Portal)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Screenshots or Videos
Browser
Edge
Additional context
No response