Summit 2014: Day 1 Takeaways

I am going to try my best to summarize what I learned on Day 1 of Summit. There was so much more information but I could not possibly process it let alone try to put it into coherent sentences. (But of course the most important piece to note is that Tony Stein called me out in the CRMUG General Session and told everyone to read my blog!!!)
Upgrading CRM – Chris Cognetta
 2015 is more like an R2 version of 2013. It is just additional features so more like an update than an upgrade.
Today 95% of CRM deployments are virtualized. This is great for Security, Disaster Recovery, etc.
Upgrade Checklist:
1.      Review upgrade path
2.      Review infrastructure set up, current users, DB Size, etc.
3.      Review User Access (web, Outlook Client, Mobile, IFD)
4.      Review usage of Jscript for security, sub grids, and web service calls
5.      Review SDK enhancements for plugins or workflow assemblies
6.      Review integrations with 3rd party IVS
7.      Review data integrations with scribe, SSIS, etc.
8.      Review data for decision on upgrade or reload
Rollup Rules: Read (make sure there is something you want), Wait (stay 1 behind)
Opening General Session: CRM 2015 – Jujhar Singh
Product Growth – Customer Service, Social Listening, Marketing and acquisition of Capptain (mobile marketing)
Sales productivity solution from Microsoft: Zero In -> Win Faster -> Sell More
Check out these slides about the future enhancements:

Techie Talk: Upgrading Complex Systems –Alex Fagundes, Jerry Weinstock
Upgrading is not a strategy, it’s a tactical exercise
CRM 2013/2015 is about 40% more efficient than CRM 2011 because of the consolidated tables.
On Premise Upgrade Scenarios: (1) In Place, (2) Connect to existing, (3) [RECOMMENDED} Side by Side
Some codeplex tools to check out to enhance your 2013 experience: (1) One Click Navigation, (2) Quickview Menu, (3) Quick Navigation
Partner Showcase: Resco Glass, wearable CRM – Ivan Stano
They have a working version of a CRM App for Google Glass – so cool!
Security and Performance – Adam Vero
Try to use a layered security model – start with a base role for all users, add roles for specific functions that ONLY contain the additional privileges
Security Roles assigned to teams are giving access based on the team (BU access would be the BU of the team NOT the user)
Access Teams are still regular teams and sharing but they remove the admin overhead of team creation. They are easier for users because they do not need to use the Share dialog and choose permissions.
Owner teams have security roles. Access teams do not have security roles.
If the Access team template is modified, this will not change any existing shares. It will only affect shares from that point forward.
When creating new lookup fields remember you are creating the RELATIONSHIP. You must think about and configure the cascading behavior.
Cascading Options for Delete:
1.      Cascade All – Kill all the orphans
2.      Remove Link – create orphan records
3.      Restrict – prevent orphan records

Leave a Reply