Skip to main content

Processing

Automatic Error Handling​

Missing Source Record​

The app fetches data from the source company and then tries to insert, modify, rename or delete the record in the destination company. Suppose the record is not found in the source company, then the following applies:

  • Insert and Modify     - For these operations we assume the exception is caused by the record being deleted immediately after the record update in the source company.     - The app will automatically skip the message if the source record no longer exists.    - An event will be logged in the Master Data Synchronisation Log.     - Although the event is logged, it will not show as a pending message in the master data activities as the app assumes there is nothing else to do.
  • Rename     - The message will be flagged as an error if the source record no longer exists.     - Here, the app requires a user because the rename action is more complex and will require investigation to ensure the data is correctly synchronised.

Missing Destination Record​

If a delete operation is performed and the record does not exist in the destination company, the app will automatically skip the message. An event will be logged in the Master Data Synchronisation Log table. Although the event is logged, it will not show as a pending message in the master data activities as the app assumes there is nothing else to do.