Skip to main content

Webservices related to Custom Tables

The notion of 'Custom Table' allows you to model the business activity specific to your use of Actito. This is possible thanks to a model of data tables directly or indirectly linked to the profile table, which stands as central element.

A license can have several specific tables, each with their own structure and their own nature (for example: offers, orders, appointments,...).

Each of these tables can be made of attributes which allow the storage of the data necessary for the purpose of this table.

For additional information regarding the data model and Custom Table, we invite you to read the chapter dedicated to 'Data Model'.

Custom Table APIs​

Moreover, we recommend that your table already contains a record, as it will let you more easily identify the structure of the table and of its components.

Custom table APIs allow you to:

tip

While creating custom tables is possible through the Actito APIs, the set-up of your data model is usually a project carried out by the Actito teams at the creation of your license. Do not hesitate to contact your account manager if you want to add tables to your data model.

Creating and updating table records​

The creation and update of custom tables is very similar to the corresponding profile tables operations. You therefore need to choose between the two options available for creating and updating custom table records: one by one or in bulk. Choosing between these two processes must be based both on the requirements of your own business activity but also on the limits regulating the use of APIs.

You should therefore ask yourself the following questions:

  • Is real-time synchronization necessary?
  • Do you need to trigger real-time scenarios?
  • Which volume are you handling?
  • Is your preferred method compatible with the call limitations?

Bulk APIs must be used when data can be accumulated until reaching a volume large enough for batch processing. The mass import API method is not meant to repeatedly post light files containing only a few records. The is indeed a limitation of 12 bulk calls per day. Moreover, mass imports are asynchronous. Posting several files at once is not an accepted practice, as they will be taken into account one after the other.

On the other hand, when the data is designed to trigger a workflow or must be immediately synchronized with the database, you should opt for one by one calls.

Should the specificities of your activity require a mix of real-time synchronization and daily synchronization, we advise you to divide your calls between mass imports and one by one calls on a case by case basis depending on the volume and immediacy required.

Step by step Use Case​

To get an overview of the process of importing custom table records one by one or in bulk, follow the Custom tables synchronization use case on the Developers Portal!