microsoftgraph / microsoftgraph/msgraph-sdk-java

Adding external reference to PlannerTaskDetails results in dangling name exception

Open
#2,505 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status:waiting-for-triage type:bug
Dominant language
Java
Stars
444
Forks
154
Avg merge
18h 28m
Merged PRs (30d)
4

Description

Describe the bug

I am using the latest version of the library, and I'm trying to add some links to PlannerTaskDetails.
Given the PlannerExternalReference is not generated for the library, I created my own record that matches the documentation ( https://learn.microsoft.com/en-us/graph/api/resources/plannerexternalreferences?view=graph-rest-1.0 besides the type, which seems wrong and doesn't match up with the explorer so I replace that with microsoft.graph.plannerExternalReference).

I have a list of URLs, so on my details => plannerExternalReferences I then call setAdditionalData with a map of String, and my PlannerExternalReference record, where the String is my url partially escaped in the same manner in the documentation.

Running this code results in an exception in the form of: dangling name https%3A//contoso%2Esharepoint%2Ecom/teams/agile/documents/AnnualReport%2Epptx

Expected behavior

To have reference(s) added to my task.

How to reproduce

Mentione in the description

SDK Version

6.55.0

Latest version known to work for scenario above?

No response

Known Workarounds

No response

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 by reproducing the PlannerTaskDetails to plannerExternalReferences flow described for SDK 6.55.0, including setAdditionalData and the custom PlannerExternalReference record. Trace how the escaped URL is handled and confirm that adding one or more references completes without the dangling name exception and produces the expected request data.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.