Why Are Files Missing from a New Application Installation?

[David Sloan]

I created a scoped application in my development instance and then published it to my repository and downloaded it on production. Some changes needed to be made, and rather than making those changes in Studio on development and republishing and upgrading, I made those changes on development and then manually made the same changes on production. Some time later I made major changes to the app on development and published version 1.1.0 of the app to my repository. When I upgraded the app on production, I found that though the installer said the installation was a success, many of the changes I had made directly on production stayed as I had edited them on production rather than upgraded to version 1.1.0. For example, I had changed the link arguments in several modules on production when we were still on version 1.0.0, and then I changed those arguments again for version 1.1.0. When I saw that these did not update, I figured my bad practice of changing things directly on production was interfering, so I completely uninstalled the app from production, deleting tables and data as well as files. Then I did a fresh install of version 1.1.0. This is working much better, but some files are missing. For example, none of the three UI pages that are listed as part of the application in studio on development were added to my production instance. Why would this be? Has anyone else had a problem with apps not completely installing?

[David Sloan]

Update: I just discovered that the UI pages are all present on production, but the record that the sys_scope field points to is missing. If I look at sys_scope.list and sys_app.list, I do not see my application or scope on production. I assume this is my problem. Can anyone tell me why when I installed the app those records were not created? It may be that I created these in development before I started working in Studio within the scoped app. If so, how can I fix that problem?

[Tom Sienkiewicz]

What you can check is go to Install log under your App record and see if there are any messages about skipped records. Then go to Upgrade History, open the log related to your install, find those skipped records and select Revert to base version. It worked for me in a similar situation. Generally I would advise against mixing repo and update sets. Publish new version to repo and you can easily update your app to the latest version. Or uninstall from prod and do a clean install from repo. Again, check the logs.

[Tom Sienkiewicz]

Also it would be really weird if the scope or app record were not included in the app itself. Check on dev, perhaps you can just use the Create Application File option to manually add them to the app if missing.