cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Helper IV
Helper IV

Mysterious error in custom connector appearing after several months and no changes

I went to go in an add another action to a custom connector I have. This would the 11th one. I've been using it for months with no issue. No I get this error when I click "Update connector"... this is with and without the new action. It just happens going into the Definition and not changing anything at all:

Specified swagger has the following errors: 'Definition is not valid. Error: 'Critical : paths/~1workspaces/post/parameters/0/schema/properties/workspace/properties/title/x-ms-visibility : The type of the property is incorrect. Expected type 'String', but value is of type 'Null'.
'

Like most MS error messages, it tells me nothing. Doesn't indicate which Action could be causing this or how to go about resolving it. To reiterate, again, nothing has changed in this connector in months. This just started to appear whether I try to add a new action, or not, just clicking "Update connector"

7 REPLIES 7
Highlighted
Super User III
Super User III

Hi @ishraqiyun77 

 

Are you getting the result as JSON? So in your schema related error field is expecting type as string.

 

"type": "string"

 

Looks like you getting null

 

Change the related field schema as follows:

 

"type": ["string", "null"]

 



Did I answer your question? Mark my post as a solution!

If you liked my response, please consider giving it a thumbs up


Proud to be a Flownaut!

Learn more from my blog

Power Automate Video Tutorials
Highlighted

Hi, not sure I'm following 100%.

Where do I make this edit? Why is this error coming up all of sudden after months of no issues?

There is nothing anywhere in the interface indicating where this error is.

I looked at the swagger editor, which Power Automate generates not me, and there are two errors:Screenshot from 2020-03-23 12-04-37.png

I resolve the issues by removing the actions associated with the errors. They aren't used anyway.

I then click "Update Connector" and get the same error. Refresh the page and the actions are back that I removed.

This error isn't preventing me from saving or doing anything and there is no explanation as to why it is here after months of no issues.

Highlighted
Frequent Visitor

I am also getting this error now when trying to edit an existing custom connector that has already been deployed.

 

So simply editing the description of a previously successfully deployed customer connector and clicking "Update Connector" now results in the following error at the top of the page

 

 

Specified swagger has the following errors: 'Definition is not valid. Error: 'Error : paths/~1convertWordDocumentFunction/post/parameters/0/schema/properties/document : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1mergeWordDocumentsFunction/post/parameters/0/schema/properties/sourcedocument : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1mergeWordDocumentsFunction/post/parameters/0/schema/properties/destinationdocument : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1convertExcelDocumentFunction/post/parameters/0/schema/properties/document : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1renderExcelChartFunction/post/parameters/0/schema/properties/document : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1convertPresentationDocumentFunction/post/parameters/0/schema/properties/document : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1formatPresentationFunction/post/parameters/0/schema/properties/document : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1mergePresentationDocumentsFunction/post/parameters/0/schema/properties/sourcedocument : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1mergePresentationDocumentsFunction/post/parameters/0/schema/properties/destinationdocument : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1convertPdfDocumentFunction/post/parameters/0/schema/properties/document : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1convertVisioDocumentFunction/post/parameters/0/schema/properties/document : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1convertOnenoteDocumentFunction/post/parameters/0/schema/properties/document : A schema with type/format 'string/binary' can only be at the top level of a body or formData parameter. ## Error : paths/~1convertHtmlFunction/post/parameters/0/schema/properties/outputformatoptions/x-ms-dynamic-schema/parameters/OutputFormat/parameter : The dynamic schema extension references properties within parameters. You need to define the 'x-ms-dynamic-properties' extension. ## Error : paths/~1convertWordDocumentFunction/post/parameters/0/schema/properties/outputformatoptions/x-ms-dynamic-schema/parameters/OutputFormat/parameter : The dynamic schema extension references properties within parameters. You need to define the 'x-ms-dynamic-properties' extension. ## Error : paths/~1convertExcelDocumentFunction/post/parameters/0/schema/properties/outputformatoptions/x-ms-dynamic-schema/parameters/OutputFormat/parameter : The dynamic schema extension references properties within parameters. You need to define the 'x-ms-dynamic-properties' extension. ## Error : paths/~1convertPresentationDocumentFunction/post/parameters/0/schema/properties/outputformatoptions/x-ms-dynamic-schema/parameters/OutputFormat/parameter : The dynamic schema extension references properties within parameters. You need to define the 'x-ms-dynamic-properties' extension. ## Error : paths/~1convertPdfDocumentFunction/post/parameters/0/schema/properties/outputformatoptions/x-ms-dynamic-schema/parameters/OutputFormat/parameter : The dynamic schema extension references properties within parameters. You need to define the 'x-ms-dynamic-properties' extension. ## Error : paths/~1convertVisioDocumentFunction/post/parameters/0/schema/properties/outputformatoptions/x-ms-dynamic-schema/parameters/OutputFormat/parameter : The dynamic schema extension references properties within parameters. You need to define the 'x-ms-dynamic-properties' extension. ## Error : paths/~1convertOnenoteDocumentFunction/post/parameters/0/schema/properties/outputformatoptions/x-ms-dynamic-schema/parameters/OutputFormat/parameter : The dynamic schema extension references properties within parameters. You need to define the 'x-ms-dynamic-properties' extension. '

 

So it looks like MS has changed the validation and broke the ability to edit and deploy the schema. 
 
Can someone from MS tell us what we are not mean't to do as this is valid Swagger 2.0 according to the editor and I can't find any blogs or documentation (which is poor for custom connectors) about any changes
Highlighted

They basically told me:




This looks like a bug with the Swagger Editor itself, which is not owned by Microsoft.  https://github.com/swagger-api/swagger-editor/issues/1972

 

The customer will need to work directly with Smartbear, who support Swagger.  We don’t support swagger design.  Smartbear would need to continue to assist them with Swagger. The Power Platforms products from Microsoft simply render the Swagger Editor from https://editor.swagger.io/ on the page.  Their Swagger code will display the same errors directly on the editor at https://editor.swagger.io/



 

Highlighted

That answer is non-sense from Microsoft.

 

So the current situation is:

1. Go the the Power Apps portal

2. Go to custom connectors

3. Select Edit

4. Click Update Connector. No changes are made and I don't switch the Swagger editor on either.

5. Receive all those definitions errors. No validation issues are shown in the front-end prior to this

 

So if you don't switch to the Swagger editor, how would you expect people to resolve these issues, or where is the migration path now you have broke peoples connectors by changing the validation applied to them.

 

This is really poor version handling

Highlighted
Advocate I
Advocate I

Getting similar error

Specified swagger has the following errors: 'Definition is not valid. Error: 'Critical : paths/~............/parameters/0/schema/properties/summary/x-ms-visibility : The type of the property is incorrect. Expected type 'String', but value is of type 'Null'.

Same situation, connector is in use and works, has been for months, now I need to add a new API call. I can't anymore.

I had some errors in the swagger editor, fixed those, but still getting this error at the top of the connector edit screen.

 

This whole custom connector stuff is so unreliable. Every time I have something to update in there or add, it ends up taking most of my day. I love the feature, cleans up a lot of my flows, but man it's so inconsistent.

Highlighted

I had a similar issue:  "Specified swagger has the following errors: 'Definition is not valid. Error: 'Error : paths/.../schema/properties/Id/default : The 'default' value is of type 'Integer', but should match the given type 'String'."

 

In my case, the API was a POST request.  The body of the message has an Id field.  I had to edit the Definition -> Request -> body -> Id and change the default value from a number to blank.  Swagger must be trying to interpret the default string value to a number, is successful, and then fails because the Id parameter should be a string.  A numeric string is still a string.  I didn't require the default value to be there as it will be filled in by the Power Automate flow anyway but it was annoying to start getting this error.

 

I know this isn't quite what others are seeing but perhaps it will point people in the right direction.

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Users online (12,034)