Knowing what an Update Preserves and Replaces

This section discusses the considerations that are important if your business requires custom modifications. An update does not change or delete any new JD Edwards EnterpriseOne object you create. However, if you modify a standard JD Edwards EnterpriseOne object or interface to an object, there may be an impact to your modifications when applying an update.

These rules describe which of your modifications the update process preserves and which modifications the update replaces.

1. "Preserve" means that during an update you do not lose your custom modifications when the software you currently have installed automatically merges them with the new JD Edwards EnterpriseOne applications shipped with the update. If there is a direct conflict between your specifications and JD Edwards EnterpriseOne specifications, the update process uses your specifications. When there is no direct conflict between the two, the update process merges the two specifications.

2. "Replace" means the update replaces your modifications and does not merge them into the update. You will need to redo your custom modifications after the update completes.

   Note: If possible, transfer all modifications to one path code. Do this only if you have tested and approved all modifications or if you have modifications only in development. Having only one environment to update significantly shortens the process.

To ensure an accurate and predictable update, follow these rules as you modify your JD Edwards EnterpriseOne objects.