Changes that were made to a scoped application are not taking effect when the updated version of the application is installed.
All Supported Releases
This is usually due to local customizations. If any changes have been made to a record locally, the system will skip this record when installing an update to the application. Thus, if any changes were made to that record in the app, they will not be applied. You can review the Skipped Changes list by going to the Upgrade History module and opening the entry for your recent application installation. From there you can use the "Revert to Base System" UI action to apply the base system version of the record from your application.
You can also determine if local changes were made by looking for sys_update_xml (Customer Update) records for the affected record. You will often find updates in the Default update set if inadvertent changes were made locally.
Use the Skipped Changes list on the Upgrade History module to review records that were skipped during the installation/update. From there you can use the "Revert to Base System" UI action to apply the base system version of the record from your application.