- Select Cloud Connector from the main menu.
-
Select the entities for which you want to generate the connector.
Loading the metadata information for elements to display the entities might take some time. Once the entities are displayed, the search tab can be used to filter the entities for selection.
Once the entity is selected (Selected Entities pane) it will no longer appear in the Available Entities pane for selection.
Notes:
Only 500 entities can be selected at any given time. As the number of selected entities increases the time taken to build the project also increases.The entities shown in the above screenshot are from:
Microsoft Dynamics 365 F&O version
2020 release wave 1
Product version : 10.0.12 (10.0.507.10024)
Platform version : Update36 (7.0.5688.35584) - Provide the name for the Connector Project to be created (and click Finish).
The actual response would look like this:
Result: Once the process completes, the Connector Project is created (see below). Application connector resources are automatically generated, mainly Business Processes and Schemas.
Each package contains object-specific Business Processes (to call the operation), and Schemas (to build Rulesets). Each Business Process has a corresponding request and response JSON Schema that can be used as part of the data transformation. You can then incorporate these resources into your overall integration solution, such as adding, updating, querying, or deleting information with MS Dynamics based on another integrated system, such as a database or flat file.
One Schema: multiple navigation entities
The current Connector now includes all navigation entities applicable for a given entity (SalesOrderHeaderV2, for example) in the response schemas of Get and GetById operations. This alleviates the manual step of merging payloads of different entities to prepare a single document (for example, displaying the merged payload in the cockpit) - something that was necessary in earlier versions of the Connector.
For example, if you execute the GetSalesOrderHeadersV2 BP, and then defined the navigation properties in the $expand query parameter (below), the response would contain the data for all the expanded navigation properties (if any). You could then map these objects using a single, expanded schema within your Ruleset.
Another use case involves an outbound Invoice. If you have SalesInvoiceHeader and SalesInvoiceLine, you can use a single API to retrieve the payload, without having to merge again.
