Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Set up document - ODBC |
Application Consultant |
Use an ODBC document to directly read data from or write data to an external database. You can exchange data with an external database via ODBC or with an external Azure SQL database. You can also exchange data with another database using CData or DB2.
|
||||||||||||||||||||||
Add document records - ODBC |
Application Consultant |
To each document, add the data records to be exchanged. For ODBC documents, set up the records in line with how the data is structured and named in the external database. This topic explains how to add records to an ODBC document. |
||||||||||||||||||||||
Manage document record setup - ODBC documents |
Application Consultant |
You have several options to manage the document record setup for ODBC documents. You can:
|
||||||||||||||||||||||
Initialize document record fields - ODBC |
Application Consultant |
For documents of type ODBC, you can initialize the fields for a record. To initialize record fields for an ODBC document, use a connector of type Database to connect to the applicable external database. Make sure, the name in the Record table field is exactly the same name as the relevant table in the external database.
The fields are added to the record based on the fields of the external table.
When the initialization is finished, review and complete the properties of the initialized fields. Usually, during review, you do not add fields. However, you can remove the not needed fields. |
||||||||||||||||||||||
Select fields - ODBC |
Application Consultant |
You can add a selection of table fields to a record. You can select fields from an external table via ODBC. To connect to the external environment, the default connector of type Database. You can set up this default connector for the applicable project. To find the external table name, the name that is defined in the Record table field is used. 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 records fields - ODBC |
Application Consultant |
To each document record, add the data fields which values must be exchanged. For ODBC documents, set up the fields in line with naming in the external database. For ODBC documents, make sure the fields have the same type as in the external database. This topic explains how to add record fields to an ODBC document. If fields are already initialized for, 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 - ODBC |
Application Consultant |
Use an ODBC document to directly read data from or write data to an external database. You can exchange data with an external database via ODBC or with an external Azure SQL database. You can also exchange data with another database using CData or DB2.
|
||||||||||||||||||||||
Add document records - ODBC |
Application Consultant |
To each document, add the data records to be exchanged. For ODBC documents, set up the records in line with how the data is structured and named in the external database. This topic explains how to add records to an ODBC document. |
||||||||||||||||||||||
Manage document record setup - ODBC documents |
Application Consultant |
You have several options to manage the document record setup for ODBC documents. You can:
|
||||||||||||||||||||||
Initialize document record fields - ODBC |
Application Consultant |
For documents of type ODBC, you can initialize the fields for a record. To initialize record fields for an ODBC document, use a connector of type Database to connect to the applicable external database. Make sure, the name in the Record table field is exactly the same name as the relevant table in the external database.
The fields are added to the record based on the fields of the external table.
When the initialization is finished, review and complete the properties of the initialized fields. Usually, during review, you do not add fields. However, you can remove the not needed fields. |
||||||||||||||||||||||
Select fields - ODBC |
Application Consultant |
You can add a selection of table fields to a record. You can select fields from an external table via ODBC. To connect to the external environment, the default connector of type Database. You can set up this default connector for the applicable project. To find the external table name, the name that is defined in the Record table field is used. 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 records fields - ODBC |
Application Consultant |
To each document record, add the data fields which values must be exchanged. For ODBC documents, set up the fields in line with naming in the external database. For ODBC documents, make sure the fields have the same type as in the external database. This topic explains how to add record fields to an ODBC document. If fields are already initialized for, 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 |
---|---|
Review and complete data migration setup |
  |