microsoftgraph / microsoftgraph/msgraph-sdk-java

Creating a Team always returns an empty Team : Cannot get the ID of the created Team.

Open
#2,238 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs: Attention :wave: type:question
Dominant language
Java
Stars
444
Forks
154
Avg merge
18h 28m
Merged PRs (30d)
4

Description

Describe the bug

Hello,

I'm using com.microsoft.graph:microsoft-graph:6.21.0 right now.

I'm trying to create a new team and then to get the ID, and the Operation ID of the result.

Team result = getGraphClient().teams().post(team);

The returned Team is always null as the JSON returned by the API is always empty. It seems that those informations are returned in the response header but I cannot access to it as the response is just a Team object.
In v5, it was returned in the object.

How am I supposed to retrieve the ID and the Operation ID of a newly created Team ?

Expected behavior

I expected that the returned Team object will contain the ID and the Operation as it was the case in the v5 of this library.

How to reproduce

Create a team with the code :

Team result = getGraphClient().teams().post(team);

The result will always be a null object.

SDK Version

6.21.0

Latest version known to work for scenario above?

5.x

Known Workarounds

None

Debug output
Click to expand log ```
</details>


### Configuration

_No response_

### Other information

_No response_

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 teams().post(team) call in the Java SDK and compare its behavior in version 6.21.0 with the reported 5.x behavior. Inspect how the create response exposes the Team ID and operation ID, then verify that the result is no longer null and both values are accessible.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.