Hi All,
I have a query about how I can provision Group Memberships (UNSAccountBInUNSGroupB) by a PowerShell connector using AdHocProjections on UNSAccountB.
I've currently configured UNSAccountB adhoc-projection (insert/update) automatically based off of UNSAccountB with no problems.
The issue is that I have now is that our Membership values are stored on the user in the target system, rather than the UNSGroupB. I've since mapped this as a virtual Property of type "Members of M:N schema types"
When the group relation (UNSAccountBInUNSGroupB) is marked as assigned i can see the XDateSubItem getting changed on the UNSGroupB.
This therefore doesn't trigger any processes (no DPRObjectOperation) as I'm only consuming groups, not pushing out Memberships from UNSGroupB so I have no need to provision out.
Looking at the documentation, I've added UNSAccountBInUNSGroupB in the PowerShell connector type sync tables. And I've enabled merging.
I've also found the following documentation, and it looks possible to do automatically send group membership changes from UNSAccountB.
https://support.oneidentity.com/technical-documents/identity-manager/8.0/target-system-synchronization-reference-guide/8#TOPIC-863235
I've followed the pre-requisites of adding CCC_XDateSubItem (Date) to the UNSAccountB table. I've also updated QBMRelation, UID_QBMRelation TSB-RL-1446 via SQL to set IsForUpdateXDateSubItem = True (because it was restricted via the object layer) which is the UNSAccountB relation in UNSAccountBInUNSGroupB
After doing this it still doesn't seem to fire an update of UNSAccountB.CCC_XDateSubItem via the underlying processes when an assignment of UNSAccountBInUNSgroupB triggers.
Thoughts on what I'm missing here?
Or is there a better way of doing this membership setting on the target user? Maybe through mapping UNSAccountBInUNSGroupB to the target system user record.
