Installing a scoped app update and getting skipped records

Thomas Weyer
Tera Contributor

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?

5 REPLIES 5

Brian O_Donnell
Tera Guru

Did you get an answer on this? I have the same question.

Found this on HI:

 

This is typically due to the record being directly updated on the target instance which is then considered a local customization by the platform.

 

To receive the updated version of the record, open the sys_upgrade_history record for the installation by going to System Diagnostics > Upgrade History. You will see the skipped record in the Skipped Changes to Review related list. From there, you can click the Revert to Base System UI action to apply the new version and ensure that it won't be skipped again in the future. 

Thomas Weyer
Tera Contributor

I have tried the proposed solution from HI.   For my scoped apps, when I click the "Revert to Base System" action, I get the following error: 

Your update version entry cannot be reverted because no base system version was found for upgrade [Application name]

Even though when I look at the version history, I can see two version records and the newest one is State = History, the older one State = Current.  

 

Any ideas?

It didn't work for me either.  Still looking for a solution.