You have several options to manage the document record setup for ODBC documents.
Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Define record sequence and structure |
Application Consultant |
You can organize the business document records in these ways:
|
||||||||||||||||||||||
View where-used |
Application Consultant |
Sometimes, if you want to clean-up your document setup, you cannot delete an element. In such a case, you can view where the element is used in the connectivity setup. You can do so for a:
|
||||||||||||||||||||||
Check relations |
Application Consultant |
For internal documents and ODBC documents, the relation between the tables of a parent record and a child record are important. The relation is required to be able to query from parent to child records in the record tree. Check or define the relation between the table for the current record and the table of the parent record. Note: If you define the parent record for an internal document and a table relation exists with the current records table, it automatically adds the first-found relation to the current record. If the relation fields are not yet added to the parent record or the current record, these are automatically added. For an ODBC document, you must set the relations manually. |
||||||||||||||||||||||
Define sorting |
Application Consultant |
For internal documents and ODBC documents, you can define the order in which the data in the record is queried and processed during export or import. For example, to export sales orders, you want the sales order to be queried by customer and for each customer by delivery date. To do so, on the Sorting tab, add a record for both the CustAccount field and the DeliveryDate field, in this sequence. |
||||||||||||||||||||||
Define range |
Application Consultant |
For each record, you can define the range of data that is queried for export or import. For example, you only want to export sales orders for a specific customer group. To do so, on the Range tab, add a record for the CustGroup field. For more information on how to define ranges in the Range field, refer to Advanced filtering and query syntax. |
||||||||||||||||||||||
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 | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Define record sequence and structure |
Application Consultant |
You can organize the business document records in these ways:
|
||||||||||||||||||||||
View where-used |
Application Consultant |
Sometimes, if you want to clean-up your document setup, you cannot delete an element. In such a case, you can view where the element is used in the connectivity setup. You can do so for a:
|
||||||||||||||||||||||
Check relations |
Application Consultant |
For internal documents and ODBC documents, the relation between the tables of a parent record and a child record are important. The relation is required to be able to query from parent to child records in the record tree. Check or define the relation between the table for the current record and the table of the parent record. Note: If you define the parent record for an internal document and a table relation exists with the current records table, it automatically adds the first-found relation to the current record. If the relation fields are not yet added to the parent record or the current record, these are automatically added. For an ODBC document, you must set the relations manually. |
||||||||||||||||||||||
Define sorting |
Application Consultant |
For internal documents and ODBC documents, you can define the order in which the data in the record is queried and processed during export or import. For example, to export sales orders, you want the sales order to be queried by customer and for each customer by delivery date. To do so, on the Sorting tab, add a record for both the CustAccount field and the DeliveryDate field, in this sequence. |
||||||||||||||||||||||
Define range |
Application Consultant |
For each record, you can define the range of data that is queried for export or import. For example, you only want to export sales orders for a specific customer group. To do so, on the Range tab, add a record for the CustGroup field. For more information on how to define ranges in the Range field, refer to Advanced filtering and query syntax. |
||||||||||||||||||||||
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 |
---|---|
Manage document record setup - ODBC documents |
  |