New Integration Introduction

Overview

TM Master integrates with external software/services using a streamlined process for importing and exporting data. The preferred method for sending data into TM Master is through its locally-hosted API. Incoming data is added to the PortalBuffer table in the database. During each service loop, TM Master processes this table to import the data, adding or updating records within the system as needed.

For exporting data, TM Master will have triggers configured based on specific events (e.g., item creation or status updates). When a trigger condition is met, the relevant data is formatted as required by the external system and added to the PortalBuffer table. During the next service loop, TM Master sends the data to the external system and logs any transmission issues.

To simplify future updates, TM Master can store and reference unique identifiers from the external system when importing or exporting data.

Technical Details

External IDs

External IDs are used in TMv2 to store unique identifiers from an external system. These are unique per “Type”(i.e Component, PO, Item etc) per external system (i.e. D365, Netsuite, SAP etc). This allows multiple integrations to be in use with one TMv2 system without the need to use existing database fields

TmPortalBuffer

This is the entry/exit point for data in and out of TM. This can be viewed as a log by the user showing the data coming in to TM from and external system and data going out. The statuses of each payload indicate the success of an import or export. Any portal buffer entries that generate an error will remain at an “error” status and produce logs for troubleshooting.

WebClients

The webclient table stores information about where to export data. For instance if we are posting data to an endpoint, the webclient row will hold the endpoint URL and the necessary information to authenticate and send (such as ID and secret). We also have a generic XML field in this table that can be used to store other information such as a token URL if token authentication is used or running numbers for the integration. The webclient records are also often used as one of multiple ways to enable/disable an integration.

Export

TMv2 tracks all changes to the database and this can be configured to triggered an export when changes are made on a table. When this is triggered we perform checks to ensure that the data should be send (if it’s PO, we might check that it’s at a relevant status) and validate the data sending (if there are required fields to send, TM ensures these are place before continuing). Once checks are passed the payload is added to the PortalBuffer awaiting to be sent.

Import

When data is received (usually through our webservice) this gets added to the Portal buffer table with a status of “Incoming”. Each service loop TM will attempt an import of all “Incoming” data, on success the status will update to “Imported”. Using ExternalIDs we can receive new, and updated data through the same interface.

Interested in an integration?

To get started, simply fill out this form and someone from the Project Management Team will be in touch shortly to get started.