General

After successful document processing in the Response object, EASY Invoice Connector returns the document number in Microsoft Dynamics 365 Business Central.

If export has not been successful, you will have to respond appropriately regarding components.

To achieve successful export, you have to export at least the following fields with values:

Export DataTool

The DataTool for export (Microsoft Business Central Connector - Export) is already part of the standard package that also contains the Import and UserExit DataTools. It consists of three components:

• the Microsoft Business Central Connector - Export DataTool itself,

• the transformation callbackscript cb.ehrmDataTools.transform.invoice2businesscentral and

• the Response-Handler-Script cb.ehrmDataTools.handler.invoice2businesscentral
  
  

The DataTool is configured such that it expects an individual file of the epiFiles file type for execution. The fields configured in the Simple selection are read from the invoice data file, transformed in the Transformation callbackscript (e.g. customizing the date format), and passed to the EASY Invoice Connector's Web service. To do this, the environment variables set for the DataTool or added to runtime are inserted in the URL. The Response Handler script processes the Microsoft Dynamics 365 Business Central or EASY Invoice Connector response by either writing back the document number (ERPProcessNumber field) or the error message (ExportServerInfo field) to the invoice data file.

Notes to integration

• Organize export after final release of the invoice/credit memo.
  
  

  • One variant is to organize export via public folders, as suggested in the sample integration.

  • But a script call at the end of the project-specific part of your approval workflow is also an option. You will then have to handle possible server responses in the workflow.

    Sample code for script call

    //#import cached [de.easy.ehrm.library.Standalone]

    try {

    const cFile = context.file;

    if (!cFile) throw new Error("no file in context.");

    const uniqueId = "de.easy.bcc.export.CHANGE_ME"; // please change this variable to the chosen unique id (advanced tab) of the respective export data tool

    const dt = new de.easy.ehrm.classes.DataToolsFactory.createByUniqueId(uniqueId, cFile),

    env = dt.getEnvironmentVariables();

    env.company = cFile.Recipient;

    dt.getDestinationService().addContext(env);

    dt.execute();

    }

    catch (ex) { c

    File.ExportServerInfo = ex;

    cFile.sync();

    util.log("execution failed. " + ex);

    }

  • The Export DataTool can also be configured as an action for the epiFiles file typed (Export DataTool, File cover, Configure action checkbox in the section Source). If this is the preferred option, you should ensure by using an AllowedActions script that the action is displayed only depending on specific conditions.
    
    

• To avoid discrepancies between the purchase invoices posted in "Microsoft Dynamics 365 Business Central" and the archive EASY Invoice purchase invoices, you should query the "Microsoft Dynamics 365 Business Central" table of the posted purchase invoices via the file ID of the current workflow and update the Documents file prior to archiving the invoice data file.

Sample integration

The following components and processes are just a suggestion of how to integrate purchase invoice data export to EASY Invoice Connector with an existing EASY Invoice workflow.

Installation and configuration

The necessary imports can be found in the example folder of the installation media. Proceed as follows:

1. Import the xml files for Public folders which you find in the /example/folder folder, using the Documents5 Manager

2. Define an existing accounting entity folder as a parent folder for the folders you have just imported (folders for accounting entities can be found below the epiData folder )

3. Import the xml file for the PortalScripts

4. Note minimum configuration of the Export DataTool (chap. Export DataTool)