Overview

Introduction

Welcome to the product documentation for Linc-Third-Party-Transactions, an extension app built for Microsoft Dynamics 365 Business Central, by Linc Communications (Pty) Ltd.

This extension contains modifications to the standard solution to assist users in importing transactions from third party systems and, through optional mapping, create sales or purchase documents, Item journals or General journals in Business Central.

Functionality

The application allows for the setup of multiple import and mapping configurations. From the imported transactions, per configuration, it is possible to create customers/vendors for the transactions, as well as convert the transactions into sales/purchase documents (orders, invoices, credit memos, return orders), Item journals or General journals.

Import methods

The following methods are supported for importing transactions from third party systems:

  • XMLPort: Text or CSV import handling object created for a specific file format by Linc and stored in this app or the customer’s app and setup for use by a specific third party configuration
  • Excel file: import object created for a specific excel file format by Linc to import directly from an Excel sheet. Launched from a separate Report object in Business Central. Both objects stored in the customer’s app.
  • API/Web Requests: Specific apps created by Linc to connect directly to a third party’s REST API’s to import transactions directly into this app using HTTP web requests
  • API Endpoints: Specific endpoints available from this app, to which third parties can connect to insert, update, delete transactions for specific applications areas/transactions types - see API Documentation

Configuration

For each external third party system and purpose, a third party setup record is required, along with additional/supplemental setup:

  • Firstly, the unique code by which to identify the specific Third Party configuration (the Third Party Code), needs to be set up in the Linc Lookup Fields & Linc Lookup Values pages
  • Then, using this new unique Third party Code, add a new configuration to the Third Party Setup page/card
  • Should any mappings be required (translations between the third party system fields and internal fields), add related setup records to the Third Party Mappings page
  • Finally, if automation of the import or processing of the imported Third Party transactions are required, setup a Job Queue Entry for this purpose

Third party setup

The Third Party Setup list page and it’s corresponding setup card page is used to specify all the setup parameters for a specific third party configuration. It is split into a few sections for different purposes:

  • the General section is used to
    • specify which application area the configuration is for (Sales/Purchases/Inventory/Financial)
    • specify which XMLPort to use (if applicable)
    • specify if mappings are to be used (if applicable)
    • specify if direct mappings are to be attempted (if applicable)
  • the Automation section is used to
    • specify the parameters required for automating the import, validating and/or processing of the third party transactions
  • the Grouping section is used to
    • specify the grouping rules for the third party configuration, which determines how different third party transaction lines will be combined into a single Sales/Purchase document
  • the Transaction section is used to
    • apply business logic when converting the third party transactions into Sales/Purchase documents and document lines
  • the Journals section is used to
    • apply business logic when converting the third party transactions into Item or General journals

See the technical documentation for more details about the fields and actions on this page

Third party mappings

Specify the optional mappings for various fields in the third party transaction table to effectively translate imported third party transaction fields to internal Business Central field values. This area also allows for the setup of splits by percentage to split one incoming third party transaction line into 2 or more document line instances.

See the technical documentation for more details about the fields and actions on this page

Job queue setup

Setup a new job queue entry for each third party transaction import to be automated, and specify the object id, parameters and recurrence to be used.

Execution

The Third Party Transactions page is where an action can be triggered to import transactions (or viewed if already imported via an automation or API integration):

  • Select the Import Transactions action from the Third Party Setup page or the Third Party Transactions page
  • If ALL of the Automation Options are switched ON in the Third Party Setup, run the associated Job Queue from Job Queue Entries page (or have it run on its recurrence schedule)
  • If only some or none of the Automation Options are switched ON in the Third Party Setup, proceed with the following steps where applicable
  • On the Third Party Transactions page, select each new row to be validated (or do a multiple selection) and select the Validate action from the Functions Menu on Third Party Transactions Page
  • If the specific third party configuration requires new customers/vendors to first be created, select the Create Customers/Vendors action from the Functions action menu of the Third Party Transactions
  • Select the Create Sales/Purchase Documents actions from Functions action menu on the Third Party Transactions page to create new Sales or Purchase documents in Business Central
  • Select the Create Item / General Journal Lines actions from Functions action menu on the Third Party Transactions page to create new Item Journal lines or General Journal lines in Business Central

See the technical documentation for more details about the fields and actions on this page