Model driven app permissions are changed on deployment

[DynAB]

This query concerns one model driven app, two solutions and two environments (DEV and TEST)

The app arrives in DEV as part of a managed solution (Project for the Web Accelerator). We have extended it by bringing it into our custom solution, adding tables, forms, views etc in the usual way. We have changed the permissions by removing some existing (PftW) roles and adding our custom roles. Examining the app in DEV shows the permissions are as we want them to be.

When we export our DEV solution as managed and deploy to TEST, the old PftW roles are back and we need to remove them manually, even though before the deployment the permissions were as we wanted them. 

Observations:

• Solution layering in TEST shows that our solution is top, above the PftWA solution
• Original deployment to TEST may well have taken place before we changed permissions on the app

Is there anything I can do about preventing this and maintaining the same set of permissions throughout all environments?

Many thanks

[AhmedSalih]

@DynAB , did you import the new Security role to your solution before exporting the solution?

[DynAB]

Thanks for the response.

We have a separate solution for roles, which is deployed alongside the main solution whenever there are changes.

I wasn't involved in the project in the early days so don't know the actual order of those first deployments.

The new roles are showing as able to access the apps fine - but the old ones keep being put back.