In a custom PowerShell connector synchronization project I do have some mappings that are split in two synchronization steps because of lookup values that are resolved later within the synchronization workflow. For example: The building mapping has a contact property mapping that refers to the user entity. The automatic dependency resolution in this case will add an additional step for resolving the contact property. In version 9.1 an optimization step has been added that does not use the
<ListingCommand Command="Get-SnowBuilding">
<SetParameter Param="Filter" Source="ConnectionParameter" DataType="String" Value="building_filter" />
<SetParameter Param="Select" Source="FixedValue" DataType="String" Value="sys_id,sys_updated_on,name" />
</ListingCommand>
<CommandSequence>
<Item Command="Get-SnowBuilding" Order="1" />
</CommandSequence>
</ReadConfiguration>
the command for retrieving a single object (see <CommandSequence> above) but instead does use the command for returning a list (see <ListingCommand>). The problem in my case is that I have an optimization for the list command to return only the key, revision and display properties and not the contact property. The optimization in the synchronization engine does not return the contact property and will clear out the value in the 1IM database. Note that if I use the single object synchronization (READ event), it will actually retrieve and populate the contact lookup value. The single object synchronization is using the same workflow but does not use the listing command. I am quite certain that this used to work in previous versions and would like to know if a fix exists or if I can set a property to block this optimization.
Rodney