An upgrade can impact custom code integrated with P6 EPPM. The upgrade brings your custom changes into the new release based on system code associated with objects. The upgrade will consider objects that are incorrectly coded to system codes obsolete and will not bring them into the upgraded version. To avoid this:
- Ensure all custom changes are coded correctly.
- Test all interfaces and customizations to ensure changes to tables, APIs, or Web Services in the upgraded software do not affect them.
- Review and update custom responsibilities and menus.
Note: In some cases, you can remove customizations after an upgrade if new features and functionality satisfy these business requirements.