Scoped app migration problems

[patricklatella]

Hi everyone.

Has anyone experienced issues with using the "Make App available on other instances" method of migrating a scoped app to a TEST (of PROD) instance?   What I'm seeing is the following:

When I migrate a scoped application I've built from DEV to TEST it is not creating a mirror image in TEST of the application that exists in DEV. Here's more detail. I've created a scoped application in our DEV instance. I am using one specific update set to hold all the updates. To migrate the application to our TEST instance I'm using the System Applications>Applications module. I select the application from the menu. I then update the "Version". I then click "Make App available on other instances"...then "Submit". I then go to our TEST instance, System Applications>Applications module. I then see the red circle in the "Updates" tab at the top. I click on it and it shows my scoped app, and I click "Update".

However when I compare the application in TEST it does not match the application in DEV. Specifically the exact setup of ACLs on the application in DEV did not transfer to TEST. And as well a list view of records from a module did not transfer.

It was my understanding that this method of migrating a custom scoped application had the same functionality as migrating update sets...where the target instance shows a mirror image of the the DEV instance (for the changes within the update set).

Anyone have experience with this?

[Pradeep Sharma]

Hello Patrick,

Can you uninstall and install the application again? I'm assuming the application is not migrated to production and is still under testing.

[patricklatella]

Hi Pradeep,

yes, it's only still in DEV and TEST.

Is that the procedure every time I need to migrate updates to the app?

[Pradeep Sharma]

Thanks for the update. This is not required with everytime you publish.

[patricklatella]

Hi again Pradeep,

I'm reluctant to try this method of deleting the app from TEST and then publishing again.   My concern is why this happened in the first place.   I've raised a HI ticket to see if I can get answers about how updates to a scoped app are handled when migrating a scoped app with this method.

Looking to the future and regarding the new app being live in PROD, if further updates done in DEV do not transfer properly, then it will not be feasible to simply delete the app from PROD to re-publish.