Access Team Template in CRM Solution

[D365Ideas_Admin]

Currently there is no way to transfer an access team template from one organization to another via solution ex- and import.
The issue is that access team templates can be configured in one org, and a form is then configured to reference this template, but the template cannot be included in a solution.

This should be handled completely analogous to configuring and tranferring Field Security Profiles for secured fields or Connection Roles, and should of course be included in a solution.

[D365Ideas_Admin]

Thanks for the feedback, we are looking at this for the mid to long term view.

[D365Ideas_Admin]

This is an annoying workaround - every time a new version is deployed to a production environment any sub-grid referencing an access team template must be re-created manually.

[D365Ideas_Admin]

I absolutely agree! But there is a "nicer" work-around for online environments. Using the Office 365 admin Portal, you can "copy" of the productive environment to your sandbox enviroments and of course to the first staging environment (packaging, customization, dev). Afterwards you do not need to modify the grids any more, because the template ID was copied with the instance.

[D365Ideas_Admin]

In some environments this will be a show stopper due to governance.

[D365Ideas_Admin]

How is it that this has still not made it into a later release? It is not possible to deploy a form using a sub-grid that refers to an Access Team Template if the template is not part of the solution. Having to use third party tools to deploy customisation components is against the principle of a self-contained system. If I can build it in the UI with point-and-click configuration / customisation, I should be able to deploy from dev to test to production using OOB solution framework.

[D365Ideas_Admin]

Wow! Three years and still no progress on what is clearly a dev team oversight. Come on, guys and gals!

Either make Access Team Templates solution-aware, or remove the functionality completely.

[LinnZawWin]

Before this idea is implemented, just use the following XrmToolBox tool to transfer from one environment to another. The tool handles even if the object type code of the entity is not the same in different environments.

https://www.xrmtoolbox.com/plugins/DynamicsCode.AccessTeamTemplateMover/

[pauwelsg]

This solution has been introduced in CRM 2013. We are now in 2020 and the feedback on this topic is that MS is looking at this for the mid to long term view? These "inconsistencies" are making our deployments really complex and painful. Should'nt be too hard to consider deployment capabilities of new functionalities at the time of developing these. Would be really appreciated that this is fixed in the very short time.