Can you clarify what the change data tab actions actually change ? - just the Extracted data or will it change data in the source fields. Im not 100 % clear on this point.

In our current scenario we wanted to flag the crm source records during an export, incrementing a counter field on them. Id hope that by setting a value in this field on the Change Data tab, that it would get updated. In test so far, this does not happen - but I am not sure if that is by design or down to the type of source system.

What is the standard / ideal method you would suggest to mark off source records during an processing run ?

All the actions in Tab 3 (Add Fields) and Tab 4 (Change Data) work on the record in memory - they do not modify the source, unless you do it explicitly using a dbupdate() or dbinsert().

Tab 3 - allows you to add new fields to the incoming record. Again, this does not modify the source data.

Tab 4 - allows you to do conditional tests on the data and modify fields.

As noted in another post, normally you would be able to use a dbupdate() statement to update your source record, and your approach would be fine. Unfortunately, when the source is Microsoft CRM, Inaport does not support the dbupdate() function because the MSCRM Web Service API does not actually implement SQL.

A work around is to create a connector to a third database, and use the dbupdate() or dbinsert() functions to log information about the CRM source data, then have a second profile that uses this data to actually update CRM.

You might also like to have a look at our blog post on creating cross reference tables during a run.

This approach offers considerable flexibility, and may be more useful for you than updating the source.

All the actions in Tab 3 (Add Fields) and Tab 4 (Change Data) work on the record in memory - they do not modify the source, unless you do it explicitly using a dbupdate() or dbinsert().

Tab 3 - allows you to add new fields to the incoming record. Again, this does not modify the source data.

Tab 4 - allows you to do conditional tests on the data and modify fields.

As noted in another post, normally you would be able to use a dbupdate() statement to update your source record, and your approach would be fine. Unfortunately, when the source is Microsoft CRM, Inaport does not support the dbupdate() function because the MSCRM Web Service API does not actually implement SQL.

A work around is to create a connector to a third database, and use the dbupdate() or dbinsert() functions to log information about the CRM source data, then have a second profile that uses this data to actually update CRM.

You might also like to have a look at our blog post on creating cross reference tables during a run.

This approach offers considerable flexibility, and may be more useful for you than updating the source.

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.