17 Aug’15

BICustomized Error Handling in Scribe Online

Consider migrating the data from Microsoft dynamics CRM online to Microsoft dynamics GP.

Our goal is after the data migration is completed successfully, we want the result of the data migration (successful/failure) to go back to the source system.


  1. Scenario:

    1st block: We query the source account entity

    2nd block: We try to update/insert the target customer entity

    3rd block: We update the source account entity, based on the result of the 2nd block (success/ failure)

    4th block: We also update the target customer block based on the result of the 2nd block (success/ failure)

  2. In the target block (Update/Insert Customer), uncheck the error handling checkbox

    [Note: Error handling checkbox, is used to check if there are any fatal errors in the executions]


  3. After the data is inserted, we can have an update block for the source entity(Update account) that will write back the result (whether the data is successfully migrated or not) to the source system.


    In this example, GP2015_CustomerUpdateInsert is for inserting the data in the target system. As we can see in field’s column, we can capture information about the previous block by the highlighted fields, which can then be stored in the source system for tracking if the data went through.

Written by

Team Member


3 thoughts on “Customized Error Handling in Scribe Online”

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • Managing mailbox through Email Archiving

    20 March’ 2018

    Introduction: Email can fill your Outlook Inbox quickly – new messages, replies, and forwards. Before you know it, yo...

    Read more
  • Workaround to Report.SAVEASPDF in NAV 2018

    20 March’ 2018

    Objective: In NAV 2017 Emailing the PDF by running the report using Report.SAVEASPDF is now not allowed in NAV 2018. Th...

    Read more
  • Dynamics 365 Client Diagnostics

    15 March’ 2018

    Main cause of Performance Issues: Bandwidth and latency are the primary characteristics which affects the performance o...

    Read more
  • Closing Blind Shift in MPOS and CPOS in Dynamics 365 for Retail

    15 March’ 2018

    Manual For closing Blind shift in POS: Blind shifts terminate the currently ongoing shift and when logged in a new shif...

    Read more
  • Persistent Filters in the Power BI Service

    13 March’ 2018

    Introduction: The feature is finally release, and it is power BI has announced general availability of persistent filt...

    Read more