I am looking into the viability of using an after script for IQService with modify operations for an Entra ID account.
Does the SailPoint.Utils.objects.AccountRequest object that is passed into the script always contain all account attributes that are configured for the source?
Hi @joseph_casale ,
In SailPoint, the ‘AccountRequest’ object that is passed into an after script typically contains the relevant attributes of the account that are being modified or created. However, it may not always include all account attributes configured for the source, especially if certain attributes are not relevant to the specific operation being performed (like an update versus a create).
Hi @Prashanth0707
If the account attribute I am concerned with is synchronized, can I expect it to always be present in a modify operation even when the value was not different?
In other words, I am trying to understand if ISC only sends the values that must be set during attribute synchronization, or if it sends all synchronized attributes and refreshes the complete set of synchronized attributes.
I am trying to write into extensionattributes in entra ID for user who are having assignedLicense attribute value as E5 and they are from a certain location type . Can someone push me in the right direction ?~~
Should I use exchange online management or a before after script would do ?
Hi @joseph_casale ,
In SailPoint, during a modify operation, the ‘AccountRequest’ object typically contains only the attributes that are being actively updated or modified, rather than all synchronized attributes. If an attribute, such as the one you are concerned with, is not being modified (i.e., its value hasn’t changed), it’s possible that it won’t be included in the request payload.