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]

I agree with you. I'll be interested to hear what they have to say.

[patricklatella]

I got an initial reply.

Regarding the ACLs, if an ACL created in DEV is migrated to TEST using this method....and then the ACL is deleted in DEV and an update is moved to TEST, then the ACL that was deleted in DEV, but was already in TEST, does NOT get deleted.

Seems odd that this would be the case, and that this would cause all kinds of issues.

[Pradeep Sharma · Accepted solution]

I didn't know that you deleted the artifacts in the new version. If that's the case then it is expected behaviour. I've shared more info in my blog here.

A guide to deleting records in scoped applications and retrieving them

[patricklatella]

To clarfiy, I had some ACLs in the scoped application, and they were moved to TEST through the "Make App available on other instances" method.  

Then I realized some of the ACLs needed to be deleted.   So I deleted them in DEV.   I then moved the application again using the "Make App available on other instances" method.   However the deleted ACLs did not delete from TEST.  

Is that expected behaviour?   An update set would not do that, correct?

Another issue is that a "Layout List" of a table did not migrate either.

[patricklatella]

Just read your blog...ok that explains a lot!   Now what about objects that don't have an active flag?