cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Sear
Frequent Visitor

Dynamic Schema in Custom Connector doesn't work suddenly

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:

 

dynamic.png

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.

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @danielbazetto 

 

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."
}}}    

}

View solution in original post

4 REPLIES 4
danielbazetto
Community Support
Community Support

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.

 

 

Hi @danielbazetto 

 

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."
}}}    

}

MatejSamler
Frequent Visitor

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? 

Sear
Frequent Visitor

Yes, this issue is resolve after I put the dynamic response in a nested object

Helpful resources

Announcements
MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Power automate tips 768x460 v2.png

Restore a Deleted Flow

Did you know that you could restore a deleted flow? Check out this helpful article.

Microsoft Build 768x460.png

Microsoft Build is May 24-26. Have you registered yet?

Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.

May UG Leader Call Carousel 768x460.png

What difference can a User Group make for you?

At the monthly call, connect with other leaders and find out how community makes your experience even better.

Top Kudoed Authors
Users online (2,969)