Table setup

Dawid Kaczmarek Updated by Dawid Kaczmarek

Tab on the Global data management form.

Tab on the Global data management form.

Adding a new table is done by choosing New and selecting the table in the Data table name field using the dropdown arrow or by typing the table name.

When the data table name has been saved it is not possible to change. If changes to the data table name is needed, click the delete button and add the correct data table name.

When the data table name has been saved it is not possible to change. If changes to the data table name is needed, click the delete button and add the correct data table name.

Please notice that global tables should NOT be shared using Cepheo GDM, as they are already shared by default in standard D365FO (e.g. Chart of accounts, Dimensions, Employees).

Owner: gives the possibility to specify an owner for the table. The owner field can be used to specify who is responsible for the GDM setup for that specific table e.g. finance department or similar. The owners must be created here: Global data management -> Setup -> Global data management owner

Index name: is the primary index on the table, it is automatically inserted when saving the data table name.

Table form: The form where the data is maintained. The Global data management button will be auto generated on this form.

Data area field: To be used for cross-company tables which has records per company, but where the ‘Data area ID’ field is not part of the table fields. Specify which field to be used instead of ‘Data area ID’, to enable creation of triggers to update records from cross-company tables. If nothing is specified in the field, then the standard ‘Data area ID’ field is used by default. If this field is specified, it is also required to run the ‘Update triggers’ job in order to apply the changes.

Menu item display: The system needs a menu item to open the Open form" on the action pane. This is specified in the field Menu item display. If the field is left BLANK, the system expects that the Table name is also the name of the menu item and will open the form with that name. It is best practice in D365FO to have a menu item with the same name as the table.

Allow create: Where the records in the table are created within the following possibilities:
None: Records can only be created from global company

Allow create global from local: Global records can be created from local companies as the user is directed to the master company. For further details see 5.2 Create/edit data.

Allow create local records: Records can be created in local companies for local use. The records created in local companies will not be created in the master company.

Allow edit: gives the user in the local entities the possibility to edit an existing record in the global data account. This will reopen the form in the Global data account and allow the user to edit the record here. When the form is closed an info might show and give the possibility pull the updated record to the local company depending on the parameter setup - see page 38.

Deletion level: how delete actions are interpreted. The Cepheo GDM allow every combination from a denial of deletion to a full cascade deletion in all companies.

Deletion level: how delete actions are interpreted. The Cepheo GDM allow every combination from a denial of deletion to a full cascade deletion in all companies.

Deletion level Only Global (cascade) or Global+local (cascade) will only delete the records local by running the Batch push data (see Batch push data) after deleting the record manual in the global company.

Documents: gives the possibility to duplicate attachments from the global data account to the local account.

Skip validation: instructs the Cepheo GDM to ignore the validate write method which is called by default in every operation. This will not skip all validation.

Sequence: the order in which the tables are synchronized.

Usage of the Sequence field

It is important to push the tables in the correct order. For example, if customers are pushed before customer groups an error can occur, because the reference to customer group on the customer is not yet synchronized in the local company.

To make sure tables are synchronized in the correct order, where the relations between tables are considered, the field Sequence must be filled in. If the sequence field is left blank, or several tables have the same sequence, then the order will be according to the table type (Main, Group etc.)

It is important to setup sequence when synchronizing tables with related tables in batch, similar to below example where CustTable uses data from CustGroup and CustGroup uses data from PaymTerm:

TableSequence
PaymTerm (Terms of payment)50
CustGroup (Customer group)60
CustTable (Customers)90

How did we do?

Table browser

InventItemGroupItem

Contact