To each document, add the data records to be exchanged. For internal documents, set up the records in line with how the data is structured and named in D365 FO.

This topic explains how to add records to documents of these types: D365 FO, Journal, or Staging.

Standard procedure

1.	Click Connectivity studio Integration Design.
2.	Click the Documents tab.
3.	In the list, find and select the desired document of one of these types: D365 FO, a journal type, or Staging.
4.	Click Edit.
5.	In the Record section, click Add line.
6.	For the record, select the D365 FO table which data must be exchanged. Usually, for internal documents, you do not change the selected value of the Record field.
	In the Record field, type a value.
7.	To structure the data records and fields in an internal document, use the D365 FO tables. The value of this field is the D365 FO table as selected in the Record field.
	In the Record table field, enter or select a value.
8.	Use the parent record to define a record structure with parent-child relations.
	In the Parent record field, enter or select a value.
9.	By default, if you have a parent-child relation, the parent and child data is processed separately. You can process the parent and child data together.
	Select Yes in the Combine with parent record field.
10.	This setting is only applicable to parent records. - Inner join: To process the parent record, the child record must exist. Example: A sales order is only processed if it has a sales line. If no sales line exists, the sales order is not processed. If a sales line exists, both the sales order and the sales line are processed. - Outer join: To process the parent record, it is not required that child a record exists. Example: A sales order with no sales lines is processed. - Exists join: To process the parent record, a child record must exist. Example: If sales order has a sales line, only the sales order is processed. If the sales order does not have a sales line, the sales order is not processed. - NoExistsJoin: Only parent records are processed that do no have child records. Example: A sales order is only processed if it does not have a sales line.
	In the Join mode field, select an option.
11.	During an import or export you can have the need to update another table in D365 FO. Usually, this is an internal history table to trace what is imported or exported. If you select Yes: - The record is skipped by the query. And therefore, not exported to an external format. - You can use the record in the message mapping. - The record uses the validations as defined in D365 FO.
	Select Yes in the History field.

See also

• Using 'Join mode' and 'Combine with parent record' on document records