microsoftgraph / microsoftgraph/msgraph-sdk-dotnet

About the Template properties on a Team

Open
#3,094 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Service issue
Dominant language
C#
Stars
789
Forks
264
Avg merge
15h 17m
Merged PRs (30d)
3

Description

Note sure if this is a bug.. but I'm a bit confused about the Templateproperty.

If I try to manually select it, or expand, the result does not contain a template object

var team = await graphServiceClient.Teams[teamId].GetAsync(requestConfiguration =>
{
   requestConfiguration.QueryParameters.Select = [nameof(Team.Template)];
}).ConfigureAwait(false);

I realize I cannot use the property Template when creating a team (I tried... but the API response makes it clear that you need to use the template@odata.bind syntax) - imho would be good to be able to). But.. why is the property there if it's never returned? I tried with select (syntax above) and with Expand, but, the value is always empty. So what's the point of having the Template property if it cannot be used when creating a new Team, and it is never returned.
And expand just tells me I cannot expand that property. So.. is there any way to determine the template that was used to create a team?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the C# Teams[teamId].GetAsync call and its Team.Template selection, then compare the behavior of $select and $expand with the Microsoft Graph API contract. Done means establishing whether Template should be returned or expanded and documenting the supported way to determine the template used to create a team.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.