Installing a scoped app update and getting skipped records

[Thomas Weyer]

I'm making minor updates to a scoped app that I developed last year.  One of these updates is to add a new field to the forms, including the Default view.  I am publishing the app to the local store in DEV, then upgrading in TEST. 

I see that some of my changes from DEV are not coming over in TEST... one is the addition of the new field on the Default view. I can see the changed record in the Application Files for the app in DEV.  After upgrading in TEST, I looked at Installation Logs and found the updated record with the following message:

Skipping because of database override:

Why is this happening and how can I fix it?

My only concern is that a fellow developer had made a change to this same form and pushed the change to TEST via an update set instead of using the internal Store to publish and upgrade. 

Ideas?

[Brian O_Donnell]

I had one record where the supplied solution didn't work, but the rest did.  For that one record, I created a UI Action on sys_update_version table. I copied the contents of the "Revert to this version" UI Action that already exists, but changed the condition to only be: current.getValue("state") != "current"

This will only work if the state of the one you want to use is history and the record marked current is an older record.

That worked to update the last one.  the Upgrade History does provide a good amount of detail that I didn't realize was available before.