v8.0 - Sync between 1IM instances - stop processes in target

How do you sync the data from A to B in your case?

And by the way, if you check the data Import flag, the FULLSYNC variable is set to false. https://support.oneidentity.com/de-de/technical-documents/identity-manager/8.0/target-system-synchronization-reference-guide/7#TOPIC-863230

Hi Markus

Not sure I understand - the sync is setup as a sync project, left side is instance A and right side is instance B. Matching key is defaultemailaddress

Does that help?

Are you using the Ad-Hoc projection or a scheduled synchronization?

One option in your templates or process chains would be to check if the change is coming from a service with this statement in your code:

IF NOT VI.Base.AppData.Instance.AppType = VI.Base.AppType.Service Then
...
End If 

Thanks Markus, its an adhoc sync. I'll try the code you gave and try it, thanks.

BTW, is that code only looking out for updates made by the job service? If so that might not work, since the attribute in instance B is updated from other sources via the job service as well. I need to stop the processes from firing specifically if the update was performed by a sync editor action

Hi Markus

That did not work, but I found something else as well.. I tried limiting the process gen condition by using (Not $XUserUpdated$.Equals("Synchronization")), but even then the process fires if the object is updated via sync. Within the process, I output XUserUpdated and interestingly it shows the old value of XUserUpdated instead of Synchronization, but via SSMS or object browser it shows Synchronization. 

It almost seems as if the UPDATE event is being triggered before the object is fully saved... can this be possible? I can't possible see the reason otherwise why the process would get fired despite the generating condition cearly ot being met.

Hi Markus

That did not work, but I found something else as well.. I tried limiting the process gen condition by using (Not $XUserUpdated$.Equals("Synchronization")), but even then the process fires if the object is updated via sync. Within the process, I output XUserUpdated and interestingly it shows the old value of XUserUpdated instead of Synchronization, but via SSMS or object browser it shows Synchronization. 

It almost seems as if the UPDATE event is being triggered before the object is fully saved... can this be possible? I can't possible see the reason otherwise why the process would get fired despite the generating condition cearly ot being met.

Using XUserUpdated in gen condition doesn't work - it seems the update event gets triggered before the XUserUpdated field is written to, so it always takes the old value. To get around this, I used Session.User.Display.ToString and that works fine

Yes, the process is generated before the object is finally saved. Both process and object are then saved in a transaction. This happens to be able to abort the save operation if an invalid process would be generated.