PowerShell: mandatory parameters in custom cmdlets – forcing the provisioning (transferring) of individual object properties. (4374953)

Apparently PoshConnector does not take ForceSyncOf properties into account when provisioning objects.

Sometimes while implementing the logic in the section of custom cmdlets of the PowerShell connector definition in such a way that some cmdlets always expect mandatory parameters, coming from objects of the schema during provisioning.

This happens while trying to force the provisioning of some object properties with the help of JobParameter “ForceSyncOf” of the Projector Component.

This will not work, because the Projector only provisions those properties that have a value in the target system that is different to the current value in the One IM database.

Adding an attribute “IsUniqueKey” to an object property in the <Schema>-section of the XML-definition would force the provisioning of the property. Unfortunately for doing this, the values in this property must be unique, which is not always the case.

Because PowerShell-module is a foundation for several other One IM connectors, it is better (and correct) to use the solution implemented in those connectors when trying to achieve the same aim, namely: the cmdlets, which require mandatory parameters, do "Reload" before "Update".

This means, that custom cmdlets must load necessary properties for given objects from the target system and then use the values of those properties when making calls with required parameters.

Use cmdlets, which require mandatory parameters, do "Reload" before "Update", so custom cmdlets must load necessary properties for given objects from the target system and then use the values of those properties when making calls with required parameters.

#34520, #445786