0
Fixed

Attribute changes don't trigger pending sync changes on a link if they are processed in a powershell task on the link

Kelly Green 11 months ago in UNIFYBroker/Plus updated by Matthew Davis (Technical Product Manager) 4 weeks ago 1

I have noticed that if a link has a PowerShell task on an outgoing sync task that modifies and sets attributes in the target, then a change flows through to only that attribute modified in the PowerShell task, then the link doesn't pick it up as pending sync change. Only running a baseline sync on the link would trigger the PowerShelltask to change/modify that attribute. 

Discussion was had with Matt Davis on the possibility of using the Register-Contribution function on a link for the attributes that are being modified through the PowerShell task to then recognise changes for those entities. However it is unsure whether the Register-Contribution function is available for links or not. As an alternative, the PowerShell script can be used on the adapter in a reverse transform, which triggers on outgoing sync changes from a link to a connector. Then the contributing attributes can be sync as direct mappings in the link.

Answer

Answer
Fixed

This has been implemented and is available in the release of UNIFYConnect V6, which will be made available shortly.

"Process unmapped changes" can be used to resolve this in the new software version, which will trigger changes for all entity fields rather than just those with direct mappings. 

Alternatively add a direct mapping for the field and override with powershell sync logic.

Answer
Fixed

This has been implemented and is available in the release of UNIFYConnect V6, which will be made available shortly.

"Process unmapped changes" can be used to resolve this in the new software version, which will trigger changes for all entity fields rather than just those with direct mappings. 

Alternatively add a direct mapping for the field and override with powershell sync logic.