Melbourne crm ug aug 2015 1tip

explore

engage

elevate

Access Team Deployment

Andre MargonoSMS Management & Technology

5th August 2015

explore engage elevate

Background: What is Access Team?

• Dynamics CRM 2013 comes up with a new feature in security called “Access Team”.• In short, Access Team is a template to provide record sharing to certain users.• This presentation won’t discuss the functionality of Access Team, so please see Further Reading at the end of the slides to learn more about Access Team functionality and also when and why you would use access team.


The Situation

• As typical project lifecycle, at minimum we would have a couple environments, such as: DEV, TEST, PROD.• As Access Team Template is not solution aware, we need to migrate the record across these environments.• First things that will come up in mind will be: ConfigurationMigration tool that is shipped with Dynamics CRM SDK. However…. It does not load “teamtemplate” (Access Team Template) entity as an option.


Some Solutions

• There are a couple suggestion in the CRM Community forum to do a DYO (Develop Your Own) console application to migrate these records across environment.

• But… It would requires CRM Development knowledge to develop the app.

• Now, for the simple and “codeless” solution…


KingswaySoft To The Rescue

• Simply create an Integration Service project in Visual Studio

• Create a package that consists of:• 1 Dynamics CRM Source that points to DEV environment

that will retrieve all “teamtemplate” records.• N number of Dynamics CRM Destinations as the target

environment• 1 Multicast action to distribute


Overall it should looks like this:


Settings for CRM Source


Settings for CRM Destination


Columns Mapping in CRM Destination


Run the package


Conclusion

• With the help of the SSIS toolkit, I could create a repeatable and codeless solution to deploy Access Team Template across different environments.

• It just took about 5 minutes to setup


Beware: Access Team Settings is Not Solution Aware!

• CRM Solution won’t carry the metadata that will change an entity to be Access Team enabled. So System Admin/Customizer need to mark them manually on each environments.


Further Reading

• Scalable Security Modeling with Microsoft Dynamics CRM 2013 (http://www.microsoft.com/en-us/download/details.aspx?id=40861)

• Use access teams and owner teams to collaborate and share information (https://msdn.microsoft.com/en-us/library/dn481569.aspx)

• Why Use Access Teams? (http://blog.crmguru.co.uk/2014/05/16/why-use-access-teams-in-dynamics-crm-2013/)

http://www.microsoft.com/en-us/download/details.aspx?id=40861

http://www.microsoft.com/en-us/download/details.aspx?id=40861

https://msdn.microsoft.com/en-us/library/dn481569.aspx

https://msdn.microsoft.com/en-us/library/dn481569.aspx

http://blog.crmguru.co.uk/2014/05/16/why-use-access-teams-in-dynamics-crm-2013/




Further Reading

• KingswaySoft Guide (http://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-crm/help-manual)

http://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-crm/help-manual

