Provisioning plan attribute requests that are set to null are removed from the operation

Hello,

I have configured a web service connector for a target, some of the values in my connector attributes can change value or be set to null.
While they appear in the provisioning plan that the value is being set to null. These attributes do not appear in the API operation to update the account.

This is an issue for because I have an attribute called end date. if the previous value was 2024-04-30 and the new value is null, the update account will not send anything for the end date and the value will still be “2024-04-30” even though it should be set to null.

I know that we can bypass this issue with a before operation rule by checking all attributes in the provisioning plan and forcing attributes that are null to be placed in the API operation. But is there any other solution for the problem?

Best regards,
Nadim

No, you’re right on the money as far as I’m aware. ISC will interpret the value as being ‘blank’ and therefore should not be entered into the body. The way to alleviate that is by catching this case with a before operation rule or alternatively, catching this with an update profile and a customized transform.

2 Likes