Use Case: Adding a Navigation Between Domains Where Imports do not Exist Out of the Box

Windchill REST Services Domain Capabilities > Customizing Domains > Recommendations When Adding Imports to the PTC-Provided Domains > Use Case: Adding a Navigation Between Domains Where Imports do not Exist Out of the Box

Consider the following example. You are trying to create a navigation between a Part (in ProdMgmt domain) and a ChangeNotice (in ChangeMgmt domain). ChangeMgmt v5 depends on DataAdmin v5, which depends on ProdMgmt v5, and ProdMgmt v5 depends on DataAdmin v5 again. If you try to customize these PTC domains by adding custom imports that are not defined by PTC, then this causes issues after an upgrade.

For example, after an upgrade, ChangeMgmt v5 domain is versioned to ChangeMgmt v6.

In this case, the customized import causes an issue of conflicting imported versions (ChangeMgmt v6 vs ChangeMgmt v5), that is, ChangeMgmt v6 -> DataAdmin v5 -> ProdMgmt v5 -> ChangeMgmt v5.

Instead of modifying OOTB PTC domains, consider these approaches:

• Approach 1: Extend Entity to Add Canonical Links to an Entity Set in Another Domain

• Approach 2: Create a Lightweight Entity Type Representation from Another Domain and Add a Navigation to that Lightweight Entity Type

• Approach 3: Create New Custom Domain with Custom Entity Representation, with Imports to PTC Domains