Skip to main content

Notifications

Power Apps - Connector Development
Suggested answer

Schema Validation error: Property "" type mismatch, Expected: "object", Actual: "string".

Like (1) ShareShare
ReportReport
Posted on 20 Sep 2024 06:24:38 by 510
Hi. I have a custom connector which has been working perfectly for over a month. It has 3 actions in it which get various results from Azure API's and I use them in a Power App.
 
Suddenly, all 3 actions are getting a 200 response but with blank response body and this schema Validation error:
Property "" type mismatch, Expected: "object", Actual: "string".
 
We have made no changes in both the Azure API's or custom connector.
The Azure API's are still producing the correct outputs in the correct formats and all my custom connector steps are successfully validated.
 
Tests from Postman work perfectly so the issue is within the Power Platform environment.
 
What do I need to look for? Has something changed in the custom connector environment on Power Platform?
  • Suggested answer
    Ammar Zaied Profile Picture
    Ammar Zaied 97 on 20 Sep 2024 at 16:13:51
    Schema Validation error: Property "" type mismatch, Expected: "object", Actual: "string".
    The error message Property "" type mismatch, Expected: "object", Actual: "string" indicates that Power Platform is expecting a different response structure from your API than what it is receiving. This can happen if there's a subtle change in the API's response format or a misalignment between the response schema defined in the custom connector and the actual output from the API.
    • Solution:
      • Revalidate the response schema in your custom connector. Compare the schema that Power Platform expects with the actual response body from Postman to ensure they are still aligned. Sometimes, small changes or additions to the response format in the Azure API can cause this type of mismatch.
      • If the API response includes optional fields that aren't always present, ensure the schema handles this by allowing nullable values or optional properties.
    Check the Power Platform release notes or any known issues that Microsoft might have published recently to see if others have encountered similar issues.
  • Suggested answer
    FLMike Profile Picture
    FLMike 27,286 on 20 Sep 2024 at 15:57:34
    Schema Validation error: Property "" type mismatch, Expected: "object", Actual: "string".
    Hi
     
    Would need to see the code, see the connector in the app, see what its doing if you just call it via a button (so that you are forced to re-use it, instead of looking at results of existing code).
     
    That or create a new Project, and add a button and that connector and see what you get.
     
    Then use Monitor to see if you get more information. You may just need to Refresh the Connector in the App.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

End of Year Newsletter…

End of Year Community Newsletter…

Tuesday Tip #12 Start your Super User…

Welcome to a brand new series, Tuesday Tips…

Tuesday Tip #11 New Opportunities…

Welcome to a brand new series, Tuesday Tips…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 144,696

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 64,456

Leaderboard

Featured topics

Loading started