microsoftgraph / microsoftgraph/msgraph-sdk-java

Dangling name error when trying to update extensionAttributes on a device

Abierto
#2,166 1 comentario 0 reacciones 1 asignado Ver en GitHub

@Ndiritu ya está trabajando en esto.

Desde el 24/10/2024.

area:serialization type:bug
Lenguaje dominante
Java
Estrellas
444
Forks
154
Merge medio
18 h 28 min
PR fusionados (30 d)
4

Descripción

Describe the bug

I am trying to update one of the extensionAttribute values within the additionalData of a device, but getting the following error:

java.lang.IllegalStateException: Dangling name: extensionAttributes

I'm following the example 2 from here - https://learn.microsoft.com/en-us/graph/api/device-update?view=graph-rest-1.0&tabs=java - although the example isn't fully complete for updating the extensionAttributes. There seems to be a model within the SDK to use for OnPremiseExtensionAttributes but not for extensionAttributes.

If I get additonalData using device.getAdditionalData() it contains the the list of the 15 extensionAttributes that can be used.

Expected behavior

Expect the extensionAttribute to update successfully, which works if updating via HTTP for example.

How to reproduce
Device newDevice = new Device();
		
Map<String,Object> additionalData = new HashMap<>();

Map<String,String> attribute = new HashMap<>();
attribute.put("extensionAttribute1", "123456");

additionalData.put("extensionAttributes", attribute);

newDevice.setAdditionalData(additionalData);

try {
	client.devices().byDeviceId(deviceId).patch(newDevice);
} catch(Exception e) {
	//handle exception
}
SDK Version

6.16.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_

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.