Table of Contents

Central layer

Tip

Make sure you are aware of the considerations when using Multiple warehouses in one administration

With Central Layer you are able to synchronize 'Master Data' between different Administrations (Companies), even if the Administrations are not in the same database. ---> Please note Important notices below for activation on correct version and platform! - marked as ** in description.

How to

  • First define C/L Partners (parties that exchange data with each other);

    • Define the CENTRAL/CL code for the central company where changes will be applied
    • Set other codes for all companies to be served from central company
    • Transport location ; DIPost web service, or Https Endpoint **
    • For each administration, setup en Endpoint. Fill in the endpoint.
    • Base URL ; Customer PROD URL **
    • Company ID ; retrieve from ID field in page 'companies'
    • Building code is only used for WMS transactions for WMS documents and stock exchange through Central Layer

  • Then define in the C/L Entities the tables to be exchanged with each other;

    • Use Initialize function to set default table selection
    • Entities are set to blocked by default when created and therefore are standard not activated
    • In Table filter you can optionally specify a filter
    • Data transfer ; Specification of all data recipients from central company
    • C/L Entity Fields ; Use to exclude fields, or set default value in de-central companies
    • Send all records ; Option to send all records in a table to a party once

  • Next: Data integration settings;

    • Central Layer Partner Id: Determines which administration belongs to which Partner, the field Partner Id is the Id of the own administration. Make sure that you don't mixed up these fields.
    • Tip: If you still want to change decentralized data, without changing table configuration, just empty this field temporarily

  • Then activate Message types in each company;

    • Message types: SND-CDM-RECORD in central company and RCV-CDM-RECORD for decentral company are used to communicate changes

  • At the end, if not activated already for other integrations, activate Job Queue 18;

    • All messages are handled through job queue function 18. You can specify a filter by means of a Parameter string, so that the C/L exchange can get a lower priority.
Tip

In the message type, specify a filter by means of a Parameter string, so that the C/L exchange can get a lower priority. ⚠ Warning: In C/L Entities, a whole table can be harmonized with Decentral companies using DataTransfer --> SEND ALL RECORDS. This will create A LOT OF messages: 1 message for each record to each partner at once!!!

Important notices

  • Minimum version 21.x
  • Master data needs to be harmonized before activating Central Layer. For example, same customers, units, items.
  • Tip: use Export Content to, for example, compare master tables using Beyond Compare.
  • Data harmonization is the responsibility of customer.
  • In case of Saas you have to use oath2, therefore you have to use version 22.x

SaaS and O-Auth2

Central partner:

Create HTTP end point for each connection:

In Http-endpoint table, for each decentral company+enviroment (PROD-RAPP-WISH-ZERO) an endpoint needs to be created and configured.

Setup HTTP end point: (field explanation)
  • URI = DIPost webservice as; https://api.businesscentral.dynamics.com...... wich also has to have an entry in '3PL App Platform Registrations'. Go to the page Web Service and lookup the SOAP url from DIPost.
  • AAD-Appcode:
    • Fill out the code and App ID provided by the customer's IT admin.
    • Set the tenant ID.
    • Specify the single-tenant account type.
    • Add the secret with an expiration date.
  • OAuth Authorization = ClientCredentials
  • Tenant ID (see login link GUIDid)
  • AAD App Scopes: https://api.businesscentral.dynamics.com/.default
  • Here, User Permission set 3PL DATAHUBSUPER can be used to retain permission.

Decentral partner:

  • In Azure Active Directory Applications, the Azure App client ID needs to be enabeled and consented by IT admin
  • Here, User Permission set 3PL DATAHUBSUPER can be used to retain permisson.
Edit this page