Resource availability to the AD customization Rule

[DivyaSubha (Divya M)]

Which IIQ version are you inquiring about?

8.4p2

Hi Team,

We are trying to set a value for custom searchable account attribute during account aggregation using “ResourceObjectCustomisation” Rule.

But while doing delta aggregation, the entire account object is not available in the rule. Just the attributes that got changed is available in the argument “object”.

Is that the expected behavior?

Can we do something to have all the attributes in the object?

Thanks

[robert-hails]

What type of application?

[neel193 (Neelmadhav Panda)]

@DivyaSubha AFAIK it depends on the connector type.

Also, if you are making it searchable, you might be aware of the this attribute will be available for other applications as well to use. So, have you considered using Account Mappings?

Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(, , etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.

[r_pragati (Pragati Rastogi)]

Delta aggregation will bring in only updated data. You can set the custom attribute using full aggregation and then run delta aggregation. Delta aggregation does not wipe out the data.

[paul_hilchey]

If your custom attribute is only dependent on one AD attribute, then you only need to set it when the AD attribute is present in the resource object.

As Pragati mentioned, the value will persist until you change it.

If it is dependent on multiple AD attributes, then that’s not so easy.