Use the journal documents to write journal data to D365 FO journals.
Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Set up document - Inventory journal |
Application Consultant |
Use an Inventory journal document to import data into the inventory journals. Compared to the D365 FO document, the Inventory journal document focuses only on the inventory journals. It has journal-specific properties and behavior. Based on the document type and journal name, the journal header is created automatically when the message is started, and the document is opened. So, in the document:
The journal name, as defined in the document header properties, defined which inventory journal is applicable. Examples of supported inventory journals are:
|
||||||||||||||||||||||
Set up document - Ledger journal |
Application Consultant |
Use a Ledger journal document to import data into the ledger journals. Compared to the D365 FO document, the Ledger journal document focuses only on the ledger journals. It has ledger-journal-specific properties and behavior. Based on the document type and journal name, the journal header is created automatically when the message is started, and the document is opened. So, in the document:
|
||||||||||||||||||||||
Set up document - Trade agreement journal |
Application Consultant |
Use a Trade agreement journal document to import data into the trade agreement journals. Compared to the D365 FO document, the Trade agreement journal document focuses only on the trade agreement journals. It has trade-agreement-journal-specific properties and behavior. Based on the document type and journal name, the journal header is created automatically when the message is started, and the document is opened. So, in the document:
|
||||||||||||||||||||||
Set up document - Other journals |
Application Consultant |
Connectivity studio provides you with several other journal-related document types:
|
||||||||||||||||||||||
Add document records - Internal document |
Application Consultant |
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. |
||||||||||||||||||||||
Manage document record setup - Internal documents |
Application Consultant |
You have several options to manage the document record setup for internal documents. You can:
|
||||||||||||||||||||||
Select fields |
Application Consultant |
You can add a selection of table fields to a record. You can select fields from the D365 FO table that is defined in the Record table field. This is mainly applicable to internal documents. However, you can also use this to quickly set up fields for external file-based documents. When the field selection is added to the record, review and complete the properties of the added fields. |
||||||||||||||||||||||
Copy fields |
Application Consultant |
You can copy fields from a record of another document. You can use this, for example, to save setup time if you use a specific record in several documents. You can only copy fields:
|
||||||||||||||||||||||
Add document record fields - Internal documents |
Application Consultant |
To each document record, add the data fields which values must be exchanged. For internal documents, set up the fields in line with naming in D365 FO. For internal documents, make sure the fields have the same type as in D365 FO. This topic explains how to add records to documents of these types: D365 FO, Journal, or Staging. If fields are already selected for or copied to the record, you can review and complete the setup for these fields. To do so, skip step 6. |
||||||||||||||||||||||
Manage document record field setup - Internal documents |
Application Consultant |
You have several options to manage the document record field setup for internal documents. You can:
|
||||||||||||||||||||||
Validate connectivity setup |
Application Consultant |
If you open a form or save (changes to) the setup of a key element in Connectivity studio, the setup is validated automatically. If errors are found in the setup, an error icon is shown. You can click the icon to show the related error messages. You can also manually start an automated test to check for errors in the setup. As a result, the found errors are shown. Also, the error icons are shown where applicable.
When errors are found, you can try to fix these errors automatically.
You can check and auto-fix errors for these key elements in Connectivity studio:
In this flow, in the activity steps, as an example, the validation is done for documents.
|
Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Set up document - Inventory journal |
Application Consultant |
Use an Inventory journal document to import data into the inventory journals. Compared to the D365 FO document, the Inventory journal document focuses only on the inventory journals. It has journal-specific properties and behavior. Based on the document type and journal name, the journal header is created automatically when the message is started, and the document is opened. So, in the document:
The journal name, as defined in the document header properties, defined which inventory journal is applicable. Examples of supported inventory journals are:
|
||||||||||||||||||||||
Set up document - Ledger journal |
Application Consultant |
Use a Ledger journal document to import data into the ledger journals. Compared to the D365 FO document, the Ledger journal document focuses only on the ledger journals. It has ledger-journal-specific properties and behavior. Based on the document type and journal name, the journal header is created automatically when the message is started, and the document is opened. So, in the document:
|
||||||||||||||||||||||
Set up document - Trade agreement journal |
Application Consultant |
Use a Trade agreement journal document to import data into the trade agreement journals. Compared to the D365 FO document, the Trade agreement journal document focuses only on the trade agreement journals. It has trade-agreement-journal-specific properties and behavior. Based on the document type and journal name, the journal header is created automatically when the message is started, and the document is opened. So, in the document:
|
||||||||||||||||||||||
Set up document - Other journals |
Application Consultant |
Connectivity studio provides you with several other journal-related document types:
|
||||||||||||||||||||||
Add document records - Internal document |
Application Consultant |
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. |
||||||||||||||||||||||
Manage document record setup - Internal documents |
Application Consultant |
You have several options to manage the document record setup for internal documents. You can:
|
||||||||||||||||||||||
Select fields |
Application Consultant |
You can add a selection of table fields to a record. You can select fields from the D365 FO table that is defined in the Record table field. This is mainly applicable to internal documents. However, you can also use this to quickly set up fields for external file-based documents. When the field selection is added to the record, review and complete the properties of the added fields. |
||||||||||||||||||||||
Copy fields |
Application Consultant |
You can copy fields from a record of another document. You can use this, for example, to save setup time if you use a specific record in several documents. You can only copy fields:
|
||||||||||||||||||||||
Add document record fields - Internal documents |
Application Consultant |
To each document record, add the data fields which values must be exchanged. For internal documents, set up the fields in line with naming in D365 FO. For internal documents, make sure the fields have the same type as in D365 FO. This topic explains how to add records to documents of these types: D365 FO, Journal, or Staging. If fields are already selected for or copied to the record, you can review and complete the setup for these fields. To do so, skip step 6. |
||||||||||||||||||||||
Manage document record field setup - Internal documents |
Application Consultant |
You have several options to manage the document record field setup for internal documents. You can:
|
||||||||||||||||||||||
Validate connectivity setup |
Application Consultant |
If you open a form or save (changes to) the setup of a key element in Connectivity studio, the setup is validated automatically. If errors are found in the setup, an error icon is shown. You can click the icon to show the related error messages. You can also manually start an automated test to check for errors in the setup. As a result, the found errors are shown. Also, the error icons are shown where applicable.
When errors are found, you can try to fix these errors automatically.
You can check and auto-fix errors for these key elements in Connectivity studio:
In this flow, in the activity steps, as an example, the validation is done for documents.
|
Related to | Notes |
---|---|
Set up journal document |
  |