OVERVIEW

Growing organizations that control more than one legal business entity are sometimes faced with the challenge of how to share data and perform inter-company transactions with partner companies.


The Multi-Company functionality of PrintVis offers synchronizing automation for data across multiple company databases or companies inside one database. Automating the replication of data reduces the effort of data maintenance.


The Multi-Company functionality of PrintVis includes:

  • Master data replication and content sharing.
  • Master data maintenance over multiple companies for Cost Centers, and their:
    • Technical specification
    • Hourly rates
    • Operations
    • Formulas
    • Speed tables
    • Scrap tables

With this standardized basic functionality it is easy to customize requirements such as: 

  • Collaboration across business entities
    • Order exchange (From headquarters, if existing)
    • Exchange of order status information (From headquarters, if existing)
  • Control across business entities
    • Inter-company postings
    • Financial and operational visibility across business entities

The following configuration are supported:


Business to business



Headquarters to business



Service Setup

On the Service Tier the following settings are required:

  • Credential Type
    • The Credential Type for this service instance must be "NavUserPassword"
  • ODATA Services
    • Setup required for the table synchronization
    • ODATA Services must be enabled
    • API Services must be enabled
  • SOAP Services
    • Setup required to import cost centers from the reference company
    • SOAP Services must be enabled


Communication Setup

Web Service

A web service is required to run the functionality:

Publish the web service with Page 6010519. 

The service name is used for the Business Group Setup. Please note: The service name must be: syncLogEntries.


The Web Service need to be set up in all connected databases!


Job Queue Setup

A job queue is required to process the data transfer. Set up and start the service with the parameters below. Set up the recurrence to your needs. If the data should be transferred as soon as possible, set up the job queue with “No. of Minutes between Runs: =1”. This means after each processing of the data changes it takes 1 minutes to run changes again.




PrintVis Business Group Setup

The Business Group setup is to connect to all databases / companies to exchange data. Create an entry for each company. This setup is required in all related companies which can be handled through synchronization. If the synchronization for the Business Group Setup is activated (see further below) it only need to be setup once and will be synchronized with to all related companies.


In the setup below, the first line is set up as "Master Company" = Yes (switch is "On"). This means this company is either:

  • A headquarters where all data is driven from, such as master data and order entry
    or
  • It is a company only to maintain master data that might not be used for order entry.



Available fields:

  • Code: Code for the Business Group
  • Name: Name for the Business Group
  • Company: The company Name to connect to
  • Master Company: Yes, this company is the master company
  • Local Currency Code: Choose the code that is the local currency (LCY) in this company.
    • This is being used to convert the currency amounts from one company to another, if the currency is different
  • API Server FQDN: Server name
    • FQDN= Fully-Qualified Host Name
  • API Servicer Port: Port Number of the ODATA service. See: Service Setup
  • API Server Instance: Server Instance
  • API Service Name: Service name must be: syncLogEntries
  • API User Name: User name for connecting to service tier
  • Password: Password for user


Data Synchronization (Master Data Sync)

Table Synchronization

Synchronization Table Setup / Sync Table Setup

By using this setup all tables can be setup for data transfer / synchronization. This is the most flexible tool to decide which data is to be transferred from one to another or all other companies. There are mandatory tables to exchange the setup and to be synchronized to all business groups. For details see the table field description below!

All required table data that is linked/required for a Cost Center setup must not be set up by using the “Synchronization Table Setup”!

The Synchronization Table Setup is stored in the cache of each session. After a change all Dynamics 365 Business Central clients need to be restarted (Windows Client)/ User needs to log out and log in again (Modern Client).


Available fields:

  • Table No.: Choose the table object no. for the synchronization
    • The following tables are mandatory and all must be set up!
      • 6010203    PVS Business Group
      • 6010515    PVS Sync Table Setup
      • 6010516    PVS Sync Field Setup
      • 6010517    PVS Sync Field Mapping
    • Table 6010347 is required only if the PrintVis Cost Centers are maintained from a master company.
  • Table Name: Displays the object name of the selected table no.
  • Sync Direction: Options
    • Master to Local
      • Data will be synchronized from the master company to all local companies that are set up in the Business group setup
    • Local to Master
      • Data will be synchronized from the local company to master company only
    • All Business Group
      • Data will be synchronized between all companies that are set up in the Business Group setup
    • Sync Order: Sequence for the synchronization
      • Required for related tables to provide date for table look-ups

Table Fields setup

The table fields mapping allows for a setup of which field of the selected table to be synchronized. By default all fields will be set to “Force Sync”.



Available fields:

  • Table No.: Table No. that is selected for the field mapping setup
  • No.: Field no. of the selected table
  • Force Sync: This field will be synchronized
  • Always Skip: This field will not be synchronized
    • This is required for data that will be maintained separately in each company and if lookup data is not even available in the local company.
  • Skip if not Empty: This field will not be synchronized, if field of the destination record is not empty.
    • With this option is it possible to maintain some fields in each local company, for example payment terms, Posting Groups etc.
  • Validate Field: Field will be validated
  • Convert to Local Currency: This field contains a currency amount that must be converted when synchronized to another company, if the currency of the destination company is different from the currency in the source company.

Field Mapping Setup

With this setup it is possible to do a value mapping for selected fields. For example posting groups could be different in each local company and with this setup no local change/maintenance of the transferred data is required.


Available fields:

  • Table No.: Table No. that is selected for the field mapping setup
  • No.: Field no. of the selected table
  • Business Group: Destination Business Group that needs a value mapping
  • From Code: Code from source company
  • To Code: Code value for the destination company


Cost Center Master Data – PV RapidStart Checklist functionality

Master data maintenance over multiple companies for Cost Centers and their:

  • Technical specification
  • Hourly rates
  • Operations
  • Formulas
  • Speed tables
  • Scrap tables

All required table data that is linked/required for a Cost Center's setup must not be manually set up by using the “Synchronization Table Setup”!

Setting it up:

Just add table 6010347 (PVS Cost Center) to the Sync Table setup:


When doing so, the related tables are added automatically (appearing in grey). The main table will be displayed in orange to indicate it’s a special table.

All settings on the main table will be taken over to the sub-tables (Active yes/no, Sync Direction, Sync Order).


Using the Master Company to create/maintain Cost Centers in local companies:

Setup in the "Master Company" only:

Create a Web Service entry for the RapidStart Service: Service Name: RapidStart


Setup in each individual local company:

Setup the Web Service URL to point to the Master Company’s Rapid Start Web Service in the PrintVis General Setup.

Make sure to specify the correct Username/password/[domain]. The web service address is the SOAP URL from the web service.



Creation of  a new Cost Center

All Cost Centers that are set up in the master company must be created ones in the local company where this Cost Center is needed. After that first creation/import, the local Cost Center will be updated from the master company after a change.

Simply from the Cost Centers List, click on “Create from Reference Company” .


Collapse the list on the right-hand side, select a department and on the left-hand side all cost centers from the same department type in the reference company will be listed.

Select the desired cost center and "Add":


Edit the data if required and click OK.




The new cost center nicely appears in the Cost Center List and is linked to the Master Company through some hidden fields:


Every time you do a change to any of the previously listed tables (related table to PVS Cost Center table in the Sync. Table setup), data will be synchronized to the local tables based on the setup between source and  Cost Center.

Synchronization Log

This table tracks all records that need to be transferred/synchronized and will show different types of records. There will be 1 entry per destination company.

Type field value can be:

  • New
    • A new record was created in the source company
  • Modify
    • A record was modified in the source company
  • Delete
    • A record was deleted in the source company

Status field can be:

  • New
    • The entry in the sync log table is new and waiting to be processed.
  • Processed
    • The entry in the sync log table has been processed successfully and the value is synchronized to the destination company.
  • Error
    • A record couldn’t be synchronized to the destination company. An error message will be displayed to identify the problem after 5 retries.




Debugging of synchronization issues

If a record couldn’t be synchronized it is possible to open the JSON data in a text file. All fields that are contained in this record synchronization will be displayed.

An error could be that a field mapping failed because the code in the source or destination company does not exist.