Recommendations When Adding Imports to the PTC-Provided Domains
If you customize the PTC out-of-the-box domains by adding new imports that are not defined by PTC, this can cause issues such as conflicting versions after an upgrade. This is mainly because either PTC domains are versioned or there are new imports.
If you are customizing an OOTB domain that needs reference to another domain and if there is no relationship between these domains out of the box, then it is recommended to avoid adding imports to the domains.
Instead of modifying OOTB domains, you can follow these approaches:
1. Extend an entity to add canonical links to an entity set in another domain.
2. Create a lightweight entity type representation from another domain (with or without canonical links) and add a navigation to that lightweight entity type.
3. Create a new custom domain with a custom entity representation, with imports to PTC domains.
 |
If you do not follow the recommended approaches and still add imports to the PTC OOTB domain, then there will be conflicting domain versions. You can use the WRS Domain Dependency Browser tool to identify the root cause and troubleshoot the errors caused by conflicting domain version imports. For more information on this tool, see Domain Dependencies Report.
|
For further information, see Use Case: Adding A Navigation Between Domains to Avoid Conflicting Domain Versions and approaches.