Scoped app migration problems

patricklatella
Mega Sage

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?

1 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


View solution in original post

39 REPLIES 39

In order to resolve this issue, log in on your dev instance and modify the list view on the custom table and push the changes to test instance. Please try this and let me know.


patricklatella
Mega Sage

OK, I'll try that.   I did that already in my last update set, I just adjusted the list view...then I reset the list view back to how I wanted it....then I moved the update set.



That resulted in the current issue of duplicated columns in the list view.



I'll try again and let you know what happens.


patricklatella
Mega Sage

ok this worked...I changed the list layout in a new update set and moved that over to TEST and it updated correctly.



thanks Pradeep!


You are very welcome Patrick.


 


Let me know if that answered your question. If so, please mark the response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list. Thank you


How To Mark Answers Correct From Community Inbox


Hi Pradeep,


one last question if I may.


So now I've got 5 update sets total that comprise all the development (that is in the app's application scope) for my scoped application.



When I go to publish the application completely to PROD for the first time, are there any potential issues I should be aware of?   The system will combine all the application scope update sets and publish the app in it's competed form?