Hello SailPoint Community,
I’ve encountered an issue while attempting to use the PATCH API to update a role’s membership criteria. My intention is to add new criteria to the ‘/membership/criteria/children’ path, but instead of adding, it seems to replace the existing membership criteria. Here’s the JSON payload I used:
[
{
"op": "add",
"path": "/membership/criteria/children",
"value": [
{
"operation": "EQUALS",
"key": {
"type": "IDENTITY",
"property": "attribute.empidcheck",
"sourceId": null
},
"stringValue": "Y",
"children": null
}
]
}
]
Based on my understanding, the add
operation should append the new criteria to the existing list at the specified path. However, it appears to behave more like a replace
operation, overwriting any existing criteria.
I’ve reviewed the documentation but couldn’t find a clear explanation for this behavior. I’m wondering if I might be misunderstanding the expected behavior of the ‘add’
operation in this context or if there might be a specific way to format the request to achieve the intended result.
Questions:
- Is the observed behavior expected when using the ‘add’ operation with the PATCH API for the ‘/membership/criteria/children’ path?
- If it’s expected, could you please advise on how to properly add new criteria without replacing the existing ones?
- Are there examples or best practices for updating membership criteria using PATCH that I might have overlooked?
I appreciate any guidance or insights you can provide on this matter. Thank you in advance for your help!
Best regards, Joy