IdentityNow Source Full Schema Update v3 API Failling

Hi there,

I was trying to update the SQL Loader source schema using v3 or beta API, but it’s failing.
Response is:
{
“detailCode”: “400.0 Bad request syntax”,
“trackingId”: “…”,
“messages”: [
{
“locale”: “en-US”,
“localeOrigin”: “DEFAULT”,
“text”: “The request could not be parsed.”
}
]
“causes”:
}

I’m trying to add a group schema (already created) reference at the section of group into the existing valid account schema:
I tried it with and without ‘id’, ‘name’, ‘created’ and ‘modified’ as it mentioned at the documentation: “Any attempt to modify these fields will result in an error response with a status code of 400.”

Could you advise what is probably wrong in my JSON request?
=====JSON start=======
{
“nativeObjectType”: “account”,
“identityAttribute”: “PersonIdExternal”,
“displayAttribute”: “PersonIdExternal”,
“hierarchyAttribute”: null,
“includePermissions”: false,
“features”: ,
“configuration”: {},
“attributes”: [
{
“name”: “PersonID”,
“type”: “STRING”,
“schema”: null,
“description”: “SAP Internal ID”,
“isMulti”: false,
“isEntitlement”: false,
“isGroup”: false
},
{
“name”: “PersonIdExternal”,
“type”: “STRING”,
“schema”: null,
“description”: “SAP External ID”,
“isMulti”: false,
“isEntitlement”: false,
“isGroup”: false
},
{
“name”: “adAccountSync”,
“type”: “STRING”,
“schema”: null,
“description”: “AD SAMAccountName”,
“isMulti”: false,
“isEntitlement”: false,
“isGroup”: false
},
{
“name”: “googleMailSync”,
“type”: “STRING”,
“schema”: null,
“description”: “GWS mail”,
“isMulti”: false,
“isEntitlement”: false,
“isGroup”: false
},
{
“name”: “IIQDisabled”,
“type”: “BOOLEAN”,
“schema”: null,
“description”: “Enabling/Disabling”,
“isMulti”: false,
“isEntitlement”: false,
“isGroup”: false
},
{
“name”: “memberOf”,
“type”: “STRING”,
“schema”: {
“type”: “CONNECTOR_SCHEMA”,
“id”: “<…>”, <= that is a real id of the existing group schema.
“name”: “group”
},
“description”: “Group Membership”,
“isMulti”: true,
“isEntitlement”: true,
“isGroup”: true
}
]
//],
// “id”: “…deleted…”,
// “name”: “account”,
// “created”: “2022-04-18T09:39:20.699Z”,
// “modified”: “2022-04-18T23:15:01.618Z”
}
============JSON end==================

Thanks in advance,
Dim.

I believe that the ID needs to remain in the body (and the URL of course). Please give it a try!

2 Likes

Hi,
Thank you, you’re right, it is working now.
“id”: and “name” original values require to be in the PUT request.

1 Like