With ITSMBridge for each form mapping you can define the primary key for
synching, i.e. either the request-id, instance id or any other field or
combination of fields that uniquely identify the record being synched. You
also have options to control behaviour when a matching record is found - either
update, skip or error. That should provide a much greater level of flexibility
to cover most data migration synching requirements.
> On 15 Feb 2017, at 23:00, arslist automatic digest system
> <lists...@arslist.org> wrote:
> arslist Digest - 12 Feb 2017 to 13 Feb 2017 (#2017-38)
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"