A bit of a strange problem this one - we use Scribe Online to insert/update records from Sage 200. If an account or contact is updated in Sage 200, the Scribe Online agent will check in Dynamics and create the record or update it if it already exists.
This all works really nicely.
The but comes here: this process seems to trigger an update of the tasks belonging to the contacts of the particular account. For example:
We had a task titled "SERVICE - 123456789". This tasks was completed by one of our users at 14/01/2016 11:17. The corresponding account was later updated in Sage 200. After Scribe Online did its stuff, the last modified date of the task was updated to 14/01/2016 16:19 and the last modified by was updated to the user that is used by Scribe Online to connect to Dynamics.
We know emphatically that the Scribe Online solution only updates the account and contact entities so that leads us to four possible causes:
- Scribe Online has a hidden process that updates tasks without being commanded to for some reason - unlikely but possible I suppose
- There is a process or business rule in Dynamics that runs "Record fields change" - we have no processes that run on tasks. There is a process that runs on accounts to automatically set the territory field but this only runs when "Record is Created". All business rules have been deactivated
- This is "by design" of Dynamics - my question is why as it appears to breach data integrity
- This is a bug in the Dynamics API
Can anyone help to shed some light on this?