Use a project as the basis for each integration. Most connectivity elements are linked to a project, for example, documents, connectors, and tasks. Because these elements are related to a project, you can also use a project to deploy connectivity setup and do version management.
Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Create project |
Application Consultant |
Use a project as the basis for each integration. For each project, you can also define the subprojects. You can use the subproject functionality to run multiple projects at once. The subprojects are run after you run the project. You can, for example, use subprojects for data migration. In this case, you set up a separate project for each applicable D365 FO module, for example, Sales and marketing, Procurement and sourcing, and Production control. Also, set up an 'umbrella' project and link the module-specific projects to it as subprojects. To run the data migration, you run the 'umbrella' project and all subprojects are automatically run as well. |
||||||||||||||||||||||
Set up applications |
Application Consultant |
Define the applications that are involved in integration or data migration projects. You can link an application to several projects. Examples of applications are:
For each connector and document, you must define the applicable application. You can also define an application for a type conversion.
External ID and revision numberApplications are also used to store the external IDs and external revision numbers that are used in the external application. You can link an external ID to a record ID in D365 FO. Together with the external ID, you can also link an external revision number to a record ID. The application, as defined for the applicable connector, is used to store the link between the reference table and record ID in D365 FO and the external ID and revision number.
If you:
|
||||||||||||||||||||||
Define project applications |
Application Consultant |
On the project, define the applications that are involved in the project. If you define an application for a connector, document, or type conversion, only the applications of the applicable project are available. The project applications are also used during export and import of the project. During project:
|
||||||||||||||||||||||
Set up default connector for project |
Application Consultant |
You can define the default connectors for the project. You can define only one default connector for each connector type.
A default connector is applied in these cases:
|
||||||||||||||||||||||
Set up web service application for project |
Application Consultant |
For an outbound web service, a connection must be established with an external web service. To connect to the external web service, for the applicable project, set up the web service application. The web service application defines the base URL for the related web service actions. If required, you can also set up the user authentication to get access to the external web service. |
||||||||||||||||||||||
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 | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Create project |
Application Consultant |
Use a project as the basis for each integration. For each project, you can also define the subprojects. You can use the subproject functionality to run multiple projects at once. The subprojects are run after you run the project. You can, for example, use subprojects for data migration. In this case, you set up a separate project for each applicable D365 FO module, for example, Sales and marketing, Procurement and sourcing, and Production control. Also, set up an 'umbrella' project and link the module-specific projects to it as subprojects. To run the data migration, you run the 'umbrella' project and all subprojects are automatically run as well. |
||||||||||||||||||||||
Set up applications |
Application Consultant |
Define the applications that are involved in integration or data migration projects. You can link an application to several projects. Examples of applications are:
For each connector and document, you must define the applicable application. You can also define an application for a type conversion.
External ID and revision numberApplications are also used to store the external IDs and external revision numbers that are used in the external application. You can link an external ID to a record ID in D365 FO. Together with the external ID, you can also link an external revision number to a record ID. The application, as defined for the applicable connector, is used to store the link between the reference table and record ID in D365 FO and the external ID and revision number.
If you:
|
||||||||||||||||||||||
Define project applications |
Application Consultant |
On the project, define the applications that are involved in the project. If you define an application for a connector, document, or type conversion, only the applications of the applicable project are available. The project applications are also used during export and import of the project. During project:
|
||||||||||||||||||||||
Set up default connector for project |
Application Consultant |
You can define the default connectors for the project. You can define only one default connector for each connector type.
A default connector is applied in these cases:
|
||||||||||||||||||||||
Set up web service application for project |
Application Consultant |
For an outbound web service, a connection must be established with an external web service. To connect to the external web service, for the applicable project, set up the web service application. The web service application defines the base URL for the related web service actions. If required, you can also set up the user authentication to get access to the external web service. |
||||||||||||||||||||||
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 |
---|---|
Define data migration project |
  |
Create test project |
  |
Define project |
  |