I have a post api which takes input or request body as such:
The "user1" and "user2" are dynamic and I first fetch the schema using TempName(I do it using x-ms-dynamic-schema in th swagger and it works fine,IN FLOW it shows me two text boxes with labels "user1" and "user2" dynamically and i can enter mark and trevor in it;for some other TempName it could show different number of text boxes). Now, my request body becomes like:
I totally oversaw the two double quotes for TempInput's value actually required(that means it is taking a string and not object) and there is no option for me to create a string dynamically in my connector. So, is there a quick fix to convert the object to string and send it as TempInput?
Solved! Go to Solution.
Hey @ChristianAbata thanks for the reply but let me clarify; I'll put an image here:
If you observe, this is my action in my custom connector: If i enter GDPR it shows me 5 boxes(dynamically): if i fill those and run the flow, the connector sends the request as
but the POST API actually expects that the TempInput be a string and not a JSON object; now I cant compromise on the UI; because I want my end user to fill his stuff in my connector's text boxes rather than fillin JSON in compose operation. So how do i workaround this? Do i change my api to accept JSON object or can I use something I am missing IN THE FLOW itself ?
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.