Microsoft-graph-docs: Cannot get the values from schemaExtension without verified domain

Created on 4 Jun 2018  路  5Comments  路  Source: microsoftgraph/microsoft-graph-docs

The schemaExtension does not show up in a query as a result if it is created without an unverified domain. E.g I've created a schemaExtension called ext46vln54c_ntest:

{
  "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#schemaExtensions/$entity",
  "id": "ext46vln54c_ntest",
  "description": "Test",
  "targetTypes": [
    "group",
    "user"
  ],
  "status": "Available",
  "owner": "677bfe9c-89e3-48a4-9009-63c6d3545ee3",
  "properties": [
    {
      "name": "AgentId",
      "type": "String"
    },
    {
      "name": "AgentExtension",
      "type": "Integer"
    },
    {
      "name": "AgentConfigurationChanged",
      "type": "DateTime"
    },
    {
      "name": "AgentLogo",
      "type": "Binary"
    }
  ]
}

I assigned this extension to an existing group(the API calls returned with 204 empty body as I expected), but somehow I can't get back the assigned values using the $select operator like this:

https://graph.microsoft.com/v1.0/groups/{GROUP_ID}?$select=ext46vln54c_ntest

First of all, I thought the API call was not successful which assigned the extension to the resource. However when I run a query and try to find the resource based on the assigned extension's then it finds the group.

https://graph.microsoft.com/v1.0/groups?$filter=ext46vln54c_ntest/AgentExtension eq 3333

``` javascript
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#groups",
"value": [
{
"id": "f810ad9f-2171-4684-b0dd-b34f7affcc4b",
"deletedDateTime": null,
"classification": null,
"createdDateTime": "2018-05-31T11:08:21Z",
"description": null,
"displayName": "FirstTestGroup2",
"groupTypes": [],
"mail": null,
"mailEnabled": false,
"mailNickname": "First",
"onPremisesLastSyncDateTime": null,
"onPremisesProvisioningErrors": [],
"onPremisesSecurityIdentifier": null,
"onPremisesSyncEnabled": null,
"preferredDataLocation": null,
"proxyAddresses": [],
"renewedDateTime": "2018-05-31T11:08:21Z",
"resourceBehaviorOptions": [],
"resourceProvisioningOptions": [],
"securityEnabled": true,
"visibility": null
}
]
}

Using the select operator it returns with empty object.

https://graph.microsoft.com/v1.0/groups?$filter=ext46vln54c_ntest/AgentExtension eq 3333&$select=ext46vln54c_ntest


``` javascript
{
  "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#groups(ext46vln54c_ntest)",
  "value": [
    {}
  ]
}

I've tested the same scenario with the built-in/existing extensions e.g. adatumisv_courses then it works properly.

Do you know how I can get the values of the assigned unverified extensions? If this is not the expected behaviour, then is there any workaround for that?

azurAAD product awaiting prod deployment

Most helpful comment

@bajzat Sorry for the delayed response. We have a code bug that we've discovered and are now fixing. Currently to get this to work, the target type values must be defined with an initial capital to get the correct behavior (when you $select later down the road). You would need to re-create your schema definition but specify "targetTypes": ["Group", "User"]. Alternatively, if you wait, our fix will roll out, which will treat the targetTypes values in a case insensitive way. At that point your $select should start working.

Sorry for the inconvenience.

All 5 comments

@bajzat Sorry for the delayed response. We have a code bug that we've discovered and are now fixing. Currently to get this to work, the target type values must be defined with an initial capital to get the correct behavior (when you $select later down the road). You would need to re-create your schema definition but specify "targetTypes": ["Group", "User"]. Alternatively, if you wait, our fix will roll out, which will treat the targetTypes values in a case insensitive way. At that point your $select should start working.

Sorry for the inconvenience.

@dkershaw10 do we have any indication on when this code bug will be released. Be good to keep this open and close it when its done.

@dkershaw10 , @jthake Thanks for the answer and the workaround. Looking forward to the fix.

@dkershaw10 has this bug fix gone out?

Forgot to close this item way back when...

Was this page helpful?
0 / 5 - 0 ratings

Related issues

fredericklin picture fredericklin  路  3Comments

joostvdlinden picture joostvdlinden  路  4Comments

Chotimir picture Chotimir  路  3Comments

gi-joe-moto picture gi-joe-moto  路  3Comments

RobinBreman picture RobinBreman  路  4Comments