Set up a connector of type D365 FO. Use this type to directly connect to a D365 FO database.
1. | Click Connectivity studio Integration Design. |
2. | Click the Connectors tab. |
3. | Click New. |
4. | In the Connector field, type a value. |
  |
Note: You are advised to not include, in the connector name, the name of the application to which you connect. Use the Application field to define the applicable application for the connector. |
5. | In the Project field, enter or select a value. |
6. | Define the applicable application for the connector. For a D365 FO connector, for example, select a 'D376 FO' application. |
  | In the Application field, enter or select a value. |
  |
Note: |
7. | Make sure, the Connector type is D365 FO. |
8. | Sub-task: Set properties. |
8.1 | Define the target company for the connector. If you want to use the active company as the target company, do not define a target company. As a result, the company from which a message is run is used as the target company. |
  | On the Properties tab, in the Target company field, enter or select a value. |
8.2 | You can use a template company as source company. If you run a message, the data is exported from the template company and imported in the target company. In a template company, you can, for example, define generally applicable master data. You can use this to set up the master data for a new company. To be able to use a template company, in the Connectivity studio parameters, define the template company for each target company. You can define several template companies. For example, with country-specific or industry-specific data. |
  | Select Yes in the Template company field. |
  |
Note: Do not define source companies if you want to use a template company. |
9. | Sub-task: Select custom handler. |
9.1 | Expand the Custom section. |
9.2 | For a D365 FO type connector, the standard handler class is BisConnectorAxDatabase. This handler class exports data from or directly imports data into D365 FO tables. You can use a customized handler class. To do so, extend the standard handler class. |
  | In the Handler field, you can enter or select a custom handler class. |
10. | Sub-task: Define source companies. |
10.1 | Define the source companies for the connector. You can define the source company for a connector in these ways: - One specific source company. - Several source companies. - No source company: Do not define a source company if you want to use the active company as the source company. As a result, the company from which a message is run is used as the source company. |
  | Expand the Source companies section. |
  |
Note: Do not define source companies if you want to use a template company. |
10.2 | Click New. |
10.3 | In the Company accounts ID field, enter or select a value. |
11. | Sub-task: Define target companies. |
11.1 | You can define several target companies for the connector. Only use this to import simple single-level master data. For example, to initialize a company. |
  | Expand the Target companies section. |
  |
Note: |
11.2 | Click New. |
11.3 | In the Company accounts ID field, enter or select a value. |
12. | Sub-task: Set advanced options. |
12.1 | Expand the Advanced options section. |
12.2 | A document can have a query for which cross-company is enabled. If a user, with access to a restricted set of companies, runs a message that uses the document, the cross-company option does not work. If you have this scenario, make sure the cross-company option is enabled for the used connector. Otherwise, you can disable the cross-company option. |
  | Select Yes in the Cross company disabled field. |
13. | Close the page. |