Installation and Configurations
Installation
Go to Extensions → Marketplace → Search for extension Dynamics 365 FO Connector → Click the install action in "actions" menu
Configurations
Configuration properties are pre-populated which user can modify as per the requirement. There are different tabs like CONNECTION, DATA FORMAT, DATA SETTINGS, ENDPOINTS, ITEM-ATTRIBUTES, MAPPINGS, MFG-ATTRIBUTES from which the user can configure the properties as shown below.
Configure the following properties from Extensions → Settings.
Setting |
Description |
Example |
3DEXPERIENCE Agent id |
3DEXPERIENCE agent id for Extension. |
- |
3DEXPERIENCE Agent secret |
3DEXPERIENCE agent secret for Extension. |
- |
Base URL to Dynamics 365 FO |
Login URL of the D365 FO. |
|
Client ID |
Username to connect to D365 FO. |
- |
Client Secret |
Password of client ID. |
- |
Grant Type |
Credentials to login |
Authorization code to use client secrets to request the token. |
Login URI |
Url to fetch the authentication token. |
| Base URL to Dynamics 365 FO, Client ID, Client Secret, 3DEXPERIENCE Agent id, 3DEXPERIENCE Agent secret need to be set by the user. |
Setting |
Description |
Example |
Case name length limit |
Used to truncate the case name up to the configured length which is supported by the D365 FO. |
10 |
File location |
Location in D365 FO to save the file. |
File/URL/Drawing, etc.. |
Is BOM lines condensed |
Decides whether to send BOM line in condensed form or not. |
true/false |
Product name length limit |
Used to truncate the product name up to the configured length which is supported by the D365 FO. |
20 |
| properties in DATA FORMAT tab need to be changed as per requirements. |
Setting |
Description |
Example |
Association Company |
- |
A001 |
Consumption Site ID |
Organization Plant ID in D365 FO |
A001 |
Consumption Warehouse ID |
Warehouse ID in D365 FO |
A001 |
Data Area ID |
Company ID in D365 FO |
A001 |
Party Number |
- |
000001234 |
Production Site ID |
Plant ID in D365 FO |
A001 |
Activity ID |
Data management import id |
1A2B3C45-D123-1234-F00L-6A123456789 |
| Activity ID value is used in Send BOM URI endpoint. |
| All properties in DATA SETTINGS are required and need to be set by the user. |
Setting |
Description |
Example |
BillOfMaterialsHeadersV2 URI |
Destination details to send BOM details of Engineering item to D365 FO. |
/data/ItemSpecificBillOfMaterialsHeadersV2 |
Case Associations URI |
Destination details to send CA details to D365 FO. |
/data/CaseAssociations |
Case Details URI |
Destination details to send case details to D365 FO. |
/data/CaseDetails |
Product Document Attachments URI |
Destination details to send attached document details of Engineering item to D365 FO |
/data/ReleasedProductDocumentAttachments |
Product Master Styles URI |
Destination details to send Product master styles details of Engineering item to D365 FO |
/data/ProductMasterStyles |
ProductsV2 URI |
Destination details to send Product details of Engineering item to D365 FO. |
/data/ProductsV2 |
ReleasedProductsV2 URI |
Destination details to send release product details of Engineering item to D365 FO. |
/data/ReleasedProductsV2 |
ReleasedProductVariantsV2 URI |
Destination details to send Product variant details of Engineering item to D365 FO. |
/data/ReleasedProductVariantsV2 |
Send BOM URI |
Destination details to send BOM details to D365 FO. |
/api/connector/enqueue/${d365.activity.id}?entity=Bill%20of%20materials%20lines%20V3 |
Service
Service corresponds to a job queue. Every event mapping needs to specify to which service it belongs. A service can be configured to run its jobs in sequence OR parallel execution. Either create a single service to handle all the events or create separate services for each event mapping.
| For more details please check Service |
Event Mapping
Event mapping holds the information about which use-case needs to be executed when the event is received. It is a binding between the event and job-request. Need to enable what events needs to be published from the DS tenant using Event Publishing app.
Example of configured events publishing are as follows.
Engineering item → Created, Status Changed, Versioned, etc…
Following event mappings are available out of the box.
Event Category |
Events |
Description |
Engineering Item |
Created |
gets invoked on creation of an engineering item in DS tenant. |
Engineering Item |
Status Changed (RELEASED) |
gets invoked on release of an engineering item in DS tenant. |
Engineering Item |
Versioned |
gets invoked on creation of new version of an engineering item in DS tenant. |
Change Action |
Created |
gets invoked on creation of change action in DS tenant. |
Change Association |
Status Changed (Complete) |
gets invoked on completion of change action in DS tenant. |
| For more details please check DS Event Mappings |
|
D365 FO connector use-cases uses token to connect to the destination url for sending the payload. |
|
In general, any D365 FO connector use-case uses the below javascript classes.
|