Hi community
We have the Problem that changes in SAP do not cause updates on the AD Account.
An example is the field DateLastWorked.
DateLastWorked goes trough the following chain:
SAP/Quickconnect
Person.Q1C_DateLastWorkedSAP
Person.DateLastWorked
ADSAccount.AccountExpires
AD Account Expires
Now if I change any of the fields in Manager (e.g. Q1C_DateLastWorkedSAP) all the Templates trigger, a Job is started, and the value in Active Directory is updated.
It also works if i change the value in Object Browser.
But it does not work if the value of Q1C_DateLastWorkedSAP is changed via the Quickconnect Sap sync. Oddly enough the template Person.DateLastWorked is executed. But not the Tempalte for ADSAccount.AccountExpires.
If I remove "If Not CBool(Variables("FULLSYNC")) Then" from the ADSAccount.AccountExpires, then ADSAccount.AccountExpires is update too, but the value in the AD itself still remains unchanged!
I have the following questions:
1. Why does this not work out of the box? Should't this be a standard case? Change something in SAP and have it provisioned all the way trough to AD. It's the same issue for other fields connected to other sources, like Person.Phone where another source System is authoritative.
2. Isn't it very dangerous to remove the "If Not CBool(Variables("FULLSYNC")) Then" part from the ADSAccount templates? Why does it have an Impact in this case?
3. As I said, when I remove the "FULLSYNC" condition, the ADSAccount Template gets triggeret. But why is there still no Job created the update the value in the AD? Shouldn't changes on ADSAccount automatically Trigger Jobs?
Again the Problem is not specific to DateLastWorked or any specific field. It seems that any changes done to Person from a Source System like SAP, only Trigger Person Templates but no ADSAccount Templates or AD Update Jobs.
Any help is appreciated!
Best regards
Philipp