Operations

In Business NXT, you can perform master type operations and sync type operations in relation to Master Data Management.

Master type operations are performed in the SyncEngine control information table, while sync type operations are performed in the SyncEngine meta information table.

Excluding certain rows from Master Data Management

You can exclude rows from Master Data Management by selecting Exclude from Master Data Management in the following fields/tables:

The Associate processing field in the Associate table
The Account processing field in the General ledger account table
The Org. unit processing on all R1-R12 tables

You can add the rows you have excluded back to Master Data Management by resetting the Exclude from Master Data Management option.

Excluding entities will trigger a synchronisation operation in SyncEngine control information table with the status Synchronisation of deletion is in progress, which means that these will get deleted in Master Data Management.

Excluding certain tables from Master Data Management

You can also exclude tables from Master Data Management.

Select the Exclude from Master Data Management field in the Company information table. There is an option for each table: R1-R12, Customer, Supplier, Contact (the Associate table is split for each master data type) and General ledger account.

Note that Customer + Supplier = the business data type for Master Data Management in the SyncEngine control information table.

You can add the tables you have excluded back to Master Data Management by resetting the Exclude from Master Data Management option.

The consequences of excluding entire tables are:

The entities corresponding to these tables will be removed from the SyncEngine meta information table.
The existing data will be synced to Master Data Management, where the existing data corresponding to the exclusion will be deleted.

Data syncing for entire table exclusions will be done via Export to Master Data Management of operation automatically.

Note:

When excluding an organisational unit table (R1-R12), the organisational unit type associated with that table will also automatically be excluded from MDM. When removing the exclusion, all the data will be imported back, including the organisational unit type. That means it will be deleted along with Rx table data from the SyncEngine meta information table, triggering a soft deletion in MDM and from there to other products sharing that data.

Resending entities to Master Data Management (entire data types)

In the SyncEngine control information table, select the rows with the desired data types. If you don’t make a selection, all rows will be processed.
Select the Resend to Master Data Management processing.

The progress of the data is indicated in the status column, from Pending to In progress. After a successful resend operation, the status field will be empty for all data types. The snapshot ID will be increased by 1, representing the next version, in sync with the Master Data Management version in Visma.net.

Exporting to Master Data Management (entire data types)

This is a more efficient way of exporting data to Master Data Management, using batches and reducing the load and failing scenarios.

In the SyncEngine control information table, select the rows with the desired data types. If you don’t make a selection, all rows will be processed.
Select the Export to Master Data Management processing.

The progress of the data is indicated in the status column, from Pending to In progress. After a successful export, the status field will be empty for all data types.

After the export to Master Data Management is finished, the data is compared with the data in Master Data Management, and every entity found in Master Data Management that doesn't exist in Business NXT will be on a list sent to Master Data Management for deletion. Please note that these deletions can affect other applications using the old data.

Note:

The snapshot ID will not be increased for this type of operation.

Note:

If the data type the import starts on has no data, then the operation will automatically switch to restore (Resend to Master Data Management) so that the data will be deleted from there too.

Updating entities of the six data types

The SyncEngine service will pick up updates in any tables that contain the six Master Data Management data types according to the poll interval set in the Visma.BusinessHost.SyncEngineService.settings.json configuration file. The sync operations will start in the SyncEngine meta information table according to the PollInterval parameter, and the progress of the data is indicated in the status column (Pending, In progress, Failed or Deleted).

After a successful update, the status field will be empty for all data types. The snapshot ID will be increased by 1, representing the next version, in sync with the Master Data Management version in Visma.net. If the company has already been enabled, the snapshot ID will continue from the previous number, according to the Master Data Management version.

Resending failed synchronisations

If any of the entities could not be sent, select the Resend failed synchronisations processing in the SyncEngine meta information table.

If the sending is successful this time, the snapshot ID will be increased by 1, representing the next version, in sync with the Master Data Management version in Visma.net. If the company has already been enabled, the snapshot ID will continue from the previous number, according to the Master Data Management version.

Resending entities

If something had happened during the sync that prevented some entities from being sent, select the entities again and run the Resend entities processing in the SyncEngine meta information table.