Answered

Unable to Save Flow which creates Teams from Template because of @odata.type

(1) Share

Report

Posted on by SDV-365Titans

I'm trying to use an HTTP call to create a Team from a template. Should be easy, below is the request body:

But because the odata.type is in there, it wont allow the Flow to save.... this is a bug for sure and a very annoying one. Anyone know if there's a solution they're working on to let us do simple things like this???


{
  "template@odata.bind": "https://graph.microsoft.com/v1.0/teamsTemplates('standard')",
  "displayName": "My New Team",
  "description": "Created from template",
  "members": [
    {
      "@odata.type": "#microsoft.graph.aadUserConversationMember",
      "roles": ["owner"],
      "user@odata.bind": "https://graph.microsoft.com/v1.0/users('user@example.com')"
    }
  ]
}

Categories:

Building flows

I have the same question (0)

All responses (15)

Answers (1)

Sort by

Pstork1 69,456 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

I just tried it with essentially your code and the flow saves fine for me. Are you getting a specific error when trying to save?

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Suggested answer

Tomac 4,105 Moderator on at

Like (1)

Report
Copy link

Link copied!
Looks like you're saying the Team isn't saving after the flow runs, rather than an issue saving the flow, correct?

Try the following in the body of your HTTP action:

{ "template@odata.bind":"https://graph.microsoft.com/v1.0/teamsTemplates('standard')", "displayName":"My Sample Team", "description":"My Sample Team’s Description", "members":[ { "@odata.type":"#microsoft.graph.aadUserConversationMember", "roles":[ "owner" ], "USER@odata.bind":"https://graph.microsoft.com/v1.0/users('USER_GUID')" } ] }

Be sure to change USER and USERGUID to match what you're using, along with the team name and description.

Also note that in your original example, you were using an email or UPN for the user in your odata.bind call instead of the GUID.

Was this reply helpful? Yes No
SDV-365Titans 20 on at

Like (1)

Report
Copy link

Link copied!

So Pstork1 can you try using the new editor? That's the one I'm using, but if it works with the old one, I guess I need to switch back for this flow.

Was this reply helpful? Yes No
SDV-365Titans 20 on at

Like (1)

Report
Copy link

Link copied!

I tried switching back to the old editor, but got the same error. Now the http action is inside a for each loop, so that might break the saving of the flow.

Was this reply helpful? Yes No
Pstork1 69,456 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Works for me in the new or the old editor. Make sure you change the email address of the user to an existing user in your system. Also make sure you aren't trying to use the Teams connector to Invoke the HTTP. The Teams resource without an object reference isn't supported in that connector. I'm not sure why it won't work for you. I copied your request body and just changed the email address.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
SDV-365Titans 20 on at

Like (1)

Report
Copy link

Link copied!

try putting the HTTP call in a nest of for-each loops, that should break it, which would mean it's a bug in PA?

or just add the json in a compose action, also throws an error:

Was this reply helpful? Yes No
Pstork1 69,456 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@SDV-365Titans Can you provide a screenshot of your flow? As you can see from my screenshot the code works fine for me in both editors. I'm trying to reproduce your error, but need more information about your specific configuration.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Suggested answer

Pstork1 69,456 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@SDV-365Titans OK, I think I know what your problem is and why it works for me. You are trying to store the body of the HTTP call in a Compose statement. That's what is keeping you from saving it. Either put the body directly in the HTTP call like I did or store it in a String Variable. The Compose action stores things in an untyped fashion, not a string. So I think that is where the problem is coming in. If you put it in a String variable or do it directly it should work. Just get rid of the Compose statement and you'll be able to save.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Tomac 4,105 Moderator on at

Like (0)

Report
Copy link

Link copied!

I see the issue. Power Automate is trying to parse @odata.type":" as an expression and it's failing because the expression is invalid.

This is definitely a bug which Microsoft will need to fix, but in the meantime can you successfully run your command without the odata.type item in your JSON?

Was this reply helpful? Yes No
Verified answer

Tomac 4,105 Moderator on at

Like (1)

Report
Copy link

Link copied!

Note that you can save the full JSON array as a string variable:

which allows you to save the flow, BUT you need to exit the editor and then go back into it before creating this variable and trying to save. Then simply reference this string variable as the body of your HTTP action.

Yeah, weird bug with weird behavior.

Was this reply helpful? Yes No