Configuration
- New legal entities (T001, T002) & added Logo
- Hide workspaces for a more clean demo experience (user level)
- Generate Number sequences
- Number sequence for Product and Item number
- Changed Number sequence for cases to manual both T001 and T002
- Changed Number sequence for BOM to manual in both T001 and T002
- Party number 3DEXPERIENCE
- Route default as “Auto” Route = List of operations
- Default Calculation group (mandatory for costing/MRP) both T001 and T002
- Product dimension group (global)
- Storage dimension group (Global)
- Tracking dimension groups (Created with Contoso, Global)
- Units (Global, created “each”)
- Site T001 & T002
- Warehouse T001 & T002
- Item model group MA (T001 & T002)
- Styles (Global)
- Create Case categories
- Create Engineering Organization
- Create Engineering Product Category Details
- Enable Batch endpoints in D365 FO system
- ECM template configuration to support UOM.
- Test create items
- Test create BOM
- Setup New Employee
- Install Deployable Package
New legal entities (T001, T002) & added Logo
| Legal entities (T001, T002) shown above are example for reference purpose only. | 
Hide workspaces for a more clean demo experience (user level)
Default company / Date, time and number format(user level)
Changed Number sequence for BOM to manual in both T001 and T002
| Need to search Bill having BOM as reference | 
Tracking dimension groups (Created with Contoso, Global)
Product Life cycle state defined as below (Global)
Enable Batch endpoints in D365 FO system
Below are the endpoint XML need to enable in D365 FO system to get data created by 3DEXPERIENCE.
<?xml version="1.0" encoding="utf-8"?>
<Document>
    <BOMBILLOFMATERIALSVERSIONDOCUMENTATTACHMENTENTITY>
        <ACCESSRESTRICTION />
        <ATTACHMENTDESCRIPTION />
        <BOMID />
        <BOMVERSIONFROMQUANTITY />
        <BOMVERSIONMANUFACTUREDITEMNUMBER />
        <BOMVERSIONPRODUCTIONSITEID />
        <BOMVERSIONPRODUCTSTYLEID />
        <DOCUMENTATTACHMENTTYPECODE />
        <NOTES />
    </BOMBILLOFMATERIALSVERSIONDOCUMENTATTACHMENTENTITY>
</Document><?xml version="1.0" encoding="utf-8"?>
<Document>
    <BOMBILLOFMATERIALSVERSIONDOCUMENTATTACHMENTENTITY>
        <ACCESSRESTRICTION />
        <ATTACHMENTDESCRIPTION />
        <BOMID />
        <BOMVERSIONFROMQUANTITY />
        <BOMVERSIONMANUFACTUREDITEMNUMBER />
        <BOMVERSIONPRODUCTIONSITEID />
        <BOMVERSIONPRODUCTSTYLEID />
        <DOCUMENTATTACHMENTTYPECODE />
        <NOTES />
    </BOMBILLOFMATERIALSVERSIONDOCUMENTATTACHMENTENTITY>
</Document>Import Project
- 
Group Name : BillOfMaterialsLinesV3 import 
Click Manage recurring data jobs in top panel
Use the ID generated above as the activity ID in the endpoint Send BOM URI defined in extension settings.
Application ID is used as client id for D365 instance in TIF configuration
- 
Group Name : Import BOMVersionDocAttachments 
Click Manage recurring data jobs in top panel
ECM template configuration to support UOM.
- 
Select Engineering change management module. 
- 
Select Released Product. 
- 
Create New Product and fill the mandatory details and click OK. 
- 
Select Engineering change management module. 
- 
Select Product release policies. 
- 
Create New policy which refers the released product created above. 
- 
Select Engineering change management module. 
- 
Select Engineering product category details. 
- 
Create new product category and map it with the policy which is created above. 
Install Deployable Package
Steps for installation
1. Make sure your deployable package folder name does not contain any white space.
2. Unlock and Unzip deployable package {tif-connector-installer-name}-<VERSION>-setup.zip from Technia to your local folder.
 
3. Close all Visual studio, SQL Server and Internet Explorer instances.
4. Open command prompt and Run as Administrator.
5. Change directory to deployable package. Command to target your folder
    cd [your deployable package folder path]
6. Run command AXUpdateInstaller.exe list to see any other runbooks which already exist.
    Make sure you don’t use already created runbook id. Create unique runbook id.
7. For creating runbook id run this command AXUpdateInstaller.exe generate -runbookid="MyRunBookId-runbook" -topologyfile="DefaultTopologyData.xml"
-servicemodelfile="DefaultServiceModelData.xml" -runbookfile="MyRunBookId-runbook.xml".
8. Now import runbook using command AXUpdateInstaller.exe import -runbookfile="MyRunBookId-runbook.xml"
9. As final step for execution run this command AXUpdateInstaller.exe execute -runbookid="MyRunBookId-runbook"
Refer below screenshot:
 
References:
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/install-deployable-package
Deployment in production:
- 
Create a deployable package from visual studio: - 
Select installed package while creating a deployable package. 
   
 
- 
- 
Creating deployable package from Devops Pipeline - 
Need to add objects in source control   
 
- 
- 
Check-in new objects. 
- 
Create a package from build pipeline. Verify that package is included in deployable package.