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 / Copilot Studio / Azure DevOps Connector...
Copilot Studio
Suggested Answer

Azure DevOps Connector error: Get Query Results

(1) ShareShare
ReportReport
Posted on by 7
The connector returned a response of type 
Record(@odata.nextLink:Blank,value:Table(System.AssignedTo:String,
System.Id:Number,System.State:String,System.Tags:Blank,System.Title:String,
System.WorkItemType:String)), 
the expected type was UnresolvedDynamicType. Error code: ConnectorOutputInvalid
Hello Community, I've been receiving this error while trying to use the connector from Copilot Studio, I was able to make it work as a powerapps flow, but not from Copilot Studio.
Any clues on why? Is there any other connector that can filter work items from Azure DevOps?
 
Best Regards,
Categories:
I have the same question (0)
  • Suggested answer
    11manish Profile Picture
    2,837 on at
    In my experience, this is more of a Copilot Studio schema-handling limitation than an Azure DevOps connector issue.
     
    Using a Power Automate wrapper flow to normalize the Azure DevOps response is typically the quickest and most reliable solution.
  • Suggested answer
    Valantis Profile Picture
    6,290 on at
     
    The error "expected type was UnresolvedDynamicType" confirms Copilot Studio can't parse the connector's dynamic response schema at runtime. This is a known limitation with connectors that return dynamic schemas in Copilot Studio tools.

    The fix: wrap the Azure DevOps call in a Power Automate flow instead of calling the connector directly from Copilot Studio.

    In the flow: call the Azure DevOps Get Query Results action, then use a Select action or Compose to map the response to a fixed schema with only the fields you need (Title, State, ID, etc.). Return that simplified array to Copilot Studio.

    This works because the flow returns a well-defined JSON structure that Copilot Studio can parse, instead of the dynamic schema the connector returns directly.
     

     

    Best regards,

    Valantis

     

    ✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

    ❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

    🏷️ For follow-ups  @Valantis.

    📝 https://valantisond365.com/

    💼 LinkedIn

    ▶️ YouTube

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 Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 249

#2
Romain The Low-Code Bearded Bear Profile Picture

Romain The Low-Code... 180 Super User 2026 Season 1

#3
Vish WR Profile Picture

Vish WR 153

Last 30 days Overall leaderboard