We're writing a custom connector and will publish it in the future, everything goes fine until two days ago(Aug 10th), the dynamic schema didn't worked, the browser returns 502 and the error message says: The response from API 'xxxxx' operation 'xxxxxx' with status code '200' does not contain a valid OpenAPI schema object, see below screenshot:
Below is the API definition that use the dynamic schema:
"200": {
"description": "Success",
"schema": {
"x-ms-dynamic-schema": {
"operationId": "Flow_GetViewRequestSchema",
"value-path": "properties",
"parameters": {
"serviceType": {
"parameter": "serviceType"
}}}}}
And below is the dynamic schema response:
{
"type": "object",
"properties": {
"department": {
"type": "string",
"x-ms-summary": "Department",
"description": "Department of the request."
}}}
I don't know what something is wrong, as it works before.
@Kaaggraw @v-litu-msft @v-bacao-msft @vbvbvb just mention some people, as this issue is urgent.
Solved! Go to Solution.
Thanks for your reply, I was able to resolve the issue by put the dynamic response in a nested object, like below(green is original one), but I sure the original one is working before :
{
properties:
{
"type": "object",
"properties": {
"department": {
"type": "string",
"x-ms-summary": "Department",
"description": "Department of the request."
}}}
}
Hello @Sear
I didn't find anything relevant on my research so far, however if this is urgent I strongly recommend you also raise a support request with the support team meanwhile.
I will continue with my search about this issue and let you know if I find something relevant.
Thanks for your reply, I was able to resolve the issue by put the dynamic response in a nested object, like below(green is original one), but I sure the original one is working before :
{
properties:
{
"type": "object",
"properties": {
"department": {
"type": "string",
"x-ms-summary": "Department",
"description": "Department of the request."
}}}
}
Hi,
I have a similar issue, where I'm migrating a Logic Apps custom connector to a Flow Custom connector.
When I put the response into properties, I lose the actual dynamic schema and I get only a "body" input field in the flow action. Did you manage to resolve it?
Yes, this issue is resolve after I put the dynamic response in a nested object
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.