When working with Microsoft Dynamics CRM Online in Enterprise there are many variables to consider. These include some of the following, but there are also small tidbits that need to be considered. I have listed some of the items below to raise the bar for everyone.
•Security, Compliance, Authentication
•Integration and Migration
•Extensions, Development and Integrations
•Enterprise Reporting
•Operations and Governance
Business Rules: CRM Business Rules are associated to each entity, when you create business rules they are stored with that entity and move with the solution that includes that entity. If you need to delete a business rule you must delete it from every environment that the solution has been deployed.
Process Workflows: In CRM v7.x.x you have the option to END a workflow. One of the issues found in the field when working on existing CRM projects are workflow designs that do not end.
Use Colors: Within the world of Dynamics CRM Online you have custom logos, colors and themes. This allows you to color code different CRM Online instance so that people in large enterprises, who have multiple CRM Online tenants and instances, don’t accidently enter data into the training environment instead of production.
Anticipate Product Line Architecture: MCS Offers a CRM PLA service for clients that need a CRM Product Line Architectural engagement to address questions on shared data, hybrid offerings, leveraging Azure, Enterprise data warehouse options and security needs? Watch out for the spread of silo'ed data that is such an easy trap for all vendors and customers to fall into.
Plug-Ins: You can change the context in which a plugin runs: By default it runs under the context of the logged in user, but there are cases when you want to run a plugin under the context of a user with different security such as a system user.
Security Roles
Security Roles are not only what you can see. All of the Out of the Box security roles contain hidden permissions that can be utilized through cloning. If you create a NEW security role, pay attention to the lack of hidden permissions that might impede functionality.
Service Module: Follow the Sun: Microsoft Dynamics CRM Service Module offers, not only an owner of a case record, but also tracking of the person working on a specific case record at any given time.
Performance: CRM Architecture does make a difference. Quick Search needs to be positioned for small searches with one or two search columns. Advanced find can be positioned for more complex queries or better yet leverage the power of the PowerBI Toolkit. You also have Enterprise Search at the top of the screen, use all your search options and even more are mentioned in the CRM Roadmap. You can also leverage the CRM Online Diagnostics Page and test form performance by Measuring Form Performance: CNTRL+SHIFT+Q
Versioning: Understanding Versioning: The Microsoft Dynamics CRM Product Team has updated their versioning, offering a clearer understanding of Major Releases, Rollup Releases and Service packs, but the true power of the experienced field engineers is knowing which feature was released with which version and the maturity of that feature. Work in partnership with Microsoft Consulting Services.
Client Software: The Outlook Client and the Unified Service Desk (USD) are client side software. One of the key questions within Enterprise are what are some options for pushing out this software. Also the client can have conflicts with certain anti-virus offerings so position and understand these conflicts and install requirements..
Working with the ISV’s: Portals: How many concurrent users was it designed for, used with and supports? Service Agreements with ISVs for outage of dependent components. Who owns updates, upgrades and testing in the fast paced release world of CRM Online?
Outlook Contacts: The Business conversation: Corporate Contacts vs. Personal Contacts and Data Migration. Do users have contacts in Outlook? How will these contacts be reconciled? How will you combine many different silos of contacts into a shared source?