web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Unable to resolve schema
Power Automate
Unanswered

Unable to resolve schema

(0) ShareShare
ReportReport
Posted on by 4

Hi

 

Can anyone out there help with a problem I'm having creating a custom connector?

I'm using the connector to post to a team channel with an in line image, something there is currently no built connector for.  I am basically copying the URL and JSON payload from the MS graph API documentation page, the 'send inline images along with messages' section of this page Send chatMessage in a channel or a chat - Microsoft Graph v1.0 | Microsoft Docs.

The URL I'm using here is https://graph.microsoft.com/v1.0/teams/{team-id}/channels/{channel-id}/messages

Having entered all of this in the Import from sample section of the definition page of new custom connector, I get the warning 'unable to resolve schema' on the body of the post.

I know the URL and payload are both valid as I can use them to post via the Graph API explorer, but when I try use the custom connector in a flow I get an error saying I need to fix expression for the input parameters.

The parameters I'm giving the connector match with the values that have worked in the graph explorer so I believe the problem is with the schema validation problem on the custom connector, but I've been able to find nothing to fix this.

Looking in the Swagger editor I do get 2 error messages about the URL parameters, but I believe this is a 'red herring' as I have another custom connector that works fine and that also shows the same error for each URL parameter.

 

Has anyone come across this problem and knows the solution?

Categories:
  • MarkKeightley Profile Picture
    4 on at

    Okay, I have found the problem after a lot of digging.

    The problem was with the JSON schema.  One of the fields starts with a @ which is used in the Work Flow Definition as described here Workflow Definition Language schema reference - Azure Logic Apps | Microsoft Docs  And as mentioned the soloution is to escape the offending character by doubling it, so @@, this still showed an error after I updated the connector, but at least the connector now works in Power Automate

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Leaderboard > Power Automate

#1
11manish Profile Picture

11manish 315 Super User 2026 Season 2

#2
Mohsin Ali Profile Picture

Mohsin Ali 267

#3
Henil Profile Picture

Henil 115

Last 30 days Overall leaderboard