Join me at CRMUG Summit 2014!


summit

 

 

 

 

It’s that time of year again, when all the CRM User base gets together for the biggest CRM user group event of the year. CRMUG Summit is a great place to learn, network and do all things CRM! Some details to the event can be found here.

If you’re attending, see my schedule below. Stop by to ask a question or just say hello!

Dynamics Partner Conference Oct 13-14

DynamicsPartnerConfernence

CRMUG Summit 2014 October 15-17
cmrug

Please note the 2:15 session has been moved to 8am that morning, giving you plenty of time to catch your flights.

I will be at both the MVP sessions.
mvp

mvp1


CRM 2015 has been announced. Fall Release 2014.


Before you say not again!, CRM 2015 has been announced and should be available by years end. From my initial testing, I can tell you we have reached a very stable, almost turning point with our common CRM platform. Now, like the ERP systems, we are going to see functionality enhancements not system re-designs, while keeping the same interface with some small enhancements around performance and usability. Multi-entity search now available out of the box! 🙂

The CRM team has really delivered, and is keeping the momentum by delivering today. A great way to sum up this new releases to others, its like CRM 2013 R2, but since we had the time, we changed the name too! 🙂

Press Release:
http://www.microsoft.com/en-us/news/press/2014/sep14/09-16crmpr.aspx
Bob Stutz’s Blog:
https://community.dynamics.com/crm/b/crmconnection/archive/2014/09/16/marketing-sales-service-one-cloud-for-all.aspx
Customer Center Get Ready Page:
http://www.microsoft.com/en-us/dynamics/crm-customer-center/get-ready-for-the-next-release.aspx


Upgrade from CRM 2011 to 2013 fails with “Subquery returned more than 1 value. Not Permitted CRM 4.0″


We recently stumbled upon an issue when upgrading a customer from CRM 4.0 to CRM 2013. As is required, you must first upgrade the 4.0 database to 2011 and then from 2011 to 2013. The 4.0 to 2011 upgrade succeeded without error but threw an error when going from 2011 to 2013. 2013 was on update rollup 2. The error thrown was:

Error| Installer Complete: OrganizationUpgrader – Error encountered
14:56:47| Error| Exception occured during Microsoft.Crm.Tools.Admin.OrganizationUpgrader: Error.ActionFailed Microsoft.Crm.Tools.Admin.InstallDatabaseUpdatesAction
InnerException: System.Data.SqlClient.SqlException (0x80131904): Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.

The statement has been terminated.

We upgraded the database from 4.0 to 2011 one afternoon and then tried going from 2011 to 2013 the following morning. As it turns out, CRM 2013 contains a query that checks to see if an organization is a new organization or an upgrade by checking the CreatedOn field of the system solution. It does this by seeing if the CreatedOn date/time is within one day (24 hours) of the current time. If the CreatedOn date of the System Solution is within 24 hours, it is considered a new organization. Here is the query:

IF EXISTS (SELECT * FROM SolutionBase WHERE SolutionId=’FD140AAD-4DF4-11DD-BD17-0019B9312238′
AND CreatedOn >= DATEADD(day, -1, GETUTCDATE()))
BEGIN

(This query goes on to Update prvAppendToOpportunity depth to global on sales person role and update prvAppendToQuote, prvAppendToOrder, prvAppendToInvoice to local on sales person role.)

When the 4.0 database is upgraded to 2011, it sets the CreatedOn date/time to whatever the UTC date/time is of that upgrade. So when going from 2011 to 2013 it sees the new date/time resulting from the upgrade to 2011 and considers it a new organization and errors out on the above query. Below is the query that can be run to check the CreatedOn date of your 2011 database.

crmquery

The easy solution to this is to just wait 24 hours between the upgrade stages but if you are in a time crunch or minimizing down time for a go-live, you can update the CreatedOn date/time of the system solution directly in the 2011 database. Remember that the time is in UTC, changing the date back one day should be easier than trying to figure out the time difference in your time zone. However, keep in mind that updating fields directly through SQL is not a change supported by Microsoft so this is done at your own risk! Not sure if this issue is isolated to just Update Rollup 2 or if this occurs with 2013 RTM, Update Rollup 1, or Service Pack 1 yet.

Thanks to my young CRM Jedi Gage Pennisi for putting the details together!


Important Dynamics CRM V Next 7.0 Release & Planning Details


Important information about supported configurations in the next release for CRM

As we ship the Microsoft Dynamics CRM 2013 Service Pack 1 and CRM Online Spring ‘14 releases, we’re looking ahead to our next release of CRM. As with other releases of CRM in the past, we find the need to add and remove items from our supported configurations list to keep current with technology, and allow us to provide you the best product possible.

Changes in supported platform software

For the next release, we’re removing the following operating systems from our Microsoft Dynamics CRM Server support matrix:
•Windows Server 2008
•Windows Server 2008 R2
•Windows Small Business Server (All versions)

We’re removing the following SQL Server versions from our Microsoft Dynamics CRM Server support matrix:
•Microsoft SQL Server 2008
•Microsoft SQL Server 2008 R2

We’re removing Microsoft Dynamics CRM for Outlook support for:
•Windows Vista
•Windows Server 2008 Remote Desktop Services
•Microsoft Office 2007

Our current plan for Microsoft Dynamics CRM Server is to target only Windows Server 2012, Windows Server 2012 R2, and SQL Server 2012 for the next release time frame.

Note that we’re exploring support for SQL Server 2014 with Microsoft Dynamics CRM Server, but we haven’t made a decision at this time.

Changes in items specific to the CRM application

Client API (JS)

We’re removing the following client SDK (JavaScript) APIs:
•GetServerUrl()
•IsOutLookClient()
•IsOutlookOnline()

This means that if your customizations are using any of these API commands, your code will likely break after you upgrade CRM.

We’re modifying the possible return values from GetFormType() to remove the ReadOnly and CRM 4.0 QuickForm Types. This means that we’re removing two values from the possible results of GetFormType(). However, it’s unlikely that your code will be affected by this because we removed the forms types in CRM 2013.

Please see Client-side Context Reference for CRM 2013 for alternative methods to use

Form system

We’re removing the following form items:
•Read-optimized forms
•CRM 2011 forms that were updated in CRM 2013

This means that you must upgrade your forms to use the new CRM 2013 form system before upgrading to the next release.

Entities

The Kit type of Product will be deprecated, which means that we’ll do base testing only and will be removing this feature in the next release. Please update your customizations to not use this entity.

Upgrade rules

We’re making database merge mandatory on upgrade. This means that you won’t be able to bypass this process during the upgrade from CRM 2013 to the next release of CRM.

Email Router

Support for Exchange 2007 connectivity to and from the CRM Email Router will be deprecated, which means that we’ll do base testing only and will be removing this capability from the CRM Email Router in a future release.

Browsers

We’re dropping support for Internet Explorer 8 and Internet Explorer 9.

Note that Internet Explorer 8 and 9 won’t route to Microsoft Dynamics CRM for phones by default, they will continue to route to the main application. However, they won’t provide an optimal experience and any issues reported will need to be validated on a supported browser.

2007 SDK SOAP Endpoint

We’ll be removing this endpoint, which was deprecated in CRM 2013. You shouldn’t use this endpoint for any new extensions.

Information provided from the Microsoft Team blog.
http://blogs.msdn.com/b/crm/archive/2014/05/14/important-information-about-supported-configurations-in-the-next-major-release-for-crm.aspx


Need to build a CRM 3 VM to Upgrade to CRM 2013? Here’s how.


We have a few customers still running CRM 3.0 after all these years. With the excitement of CRM 2013, they have decided to upgrade at one shot. Dynamics CRM 3.0 can upgrade to CRM 4.0, or one version at a time. The users don’t have be aware of this step, only the end game which is CRM 2013.

In order to process this change, and migrate the customer to the cloud, we need to upgrade their systems. In order to do this, I decided to build a VM in order to upgrade CRM 3.0 to 4.0, and then will use my 2011 VM to upgrade to 2011, then insert DB into the new CRM 2013 development system.

Easier said than done Right? I really had to dig into my memory banks to remember the process, and thought it would be helpful to others to have it accessible. So Here we go:

1. Build a Windows Server 2003 R2 Standard build VM
2. Make sure you add enough disc space to cover the size of your production database, zipped and unzipped together. I’m using 60 gigs, 2 processors and 2.5 gigs of memory in the VM.
3. Add the Domain Controller and Application Server Roles (select ASP.NET as well).
4. Reboot
5. Install SQL Server 2005 with reporting services. You must configure reporting services as well.
** CRM 3.0 started on SQL2000, and was commonly upgraded to SQL2005. The CRM 3.0 installation download includes the fixes to work with SQL2005. In the past we had to install it on SQL 2000, upgrade SQL2005 after.
6. Test Access to Reporting services once completed.
7. Copy the production CRM 3.0 database and unzip on this VM.
** Make sure you copy both ORGNAME_MSCRM and ORGNAME_METABASE as these were separate DBS in CRM 3.0
8. Restore CRM 3.0 database to the SQL Server.
9. On the CRM 3.0 CD, explore and run the redeployment tool .MSI.
10. Run the CRM 3.0 redeployment tool, enter server name localhost and select the production DBs.
11. Choose to manually map, and find a user account of administrator, mapping your VM admin id.
12. Let redeployment complete.
13. Launch the CRM 3.0 installation, and proceed with setup. When you enter the SQL Server (localhost) you will be able to connect to an existing deployment. Choose your databases here.

That will get CRM 3.0 running again in your VM. Please note that all ISV’s etc should be removed as they will no longer work. You could have manually cleanup unless you run the uninstallers of these applications in production.

You might also want to consider using a P to V technology (Physical to Virtual) to build the VM exactly as it is in production but Virtual.

Enjoy!


CRM 2013 Upgrade Flurry has Started! Upgrade Checklist


Microsoft has begun switching over many of our Microsoft Dynamics CRM customers to CRM 2013.

Here’s some things you should know about the overall process:

1. Ensure you have another environment (test/dev) that matches your CRM production setup.
This is a best practice by far. Not having a test environment, makes troubleshooting and changes in your production environment almost impossible to manage. This is no different for which deployment model you have choose: Online, On-Premise or Partner Hosted.

Ensure this environment has a copy of the latest customizations, solutions, ISV’s etc. Data can also be replicated from production, using tools like the CRM 2011 Instance Adapter or tool like Scribe.

If you do not have a CRM 2011 instance for test/dev. already, its now too late to create a new one as only CRM 2013 instances are available as of Nov 4th. You will have no choice but to create a test CRM 2013 trial and import your 2011 solution which if fully supported. This will provide you with what your system will look like after the upgrade.

You should also push out your production CRM Online date as far as possible. Today, the last date available to upgrade is 2/14/2014. For other implementations, you still have some time :).

2. Understanding your Environment
Ensuring that your understand all the components that have been deployed with your CRM system is critical to the success of your upgrade. You will need to review all your Solutions, Web Resources and Custom Code to ensure that your and your ISV’s are prepared for the upgrade.

Microsoft has provided a tool to help pin point this issues.
http://www.microsoft.com/en-us/download/details.aspx?id=30151

The information provided by the tool will be a roadmap for your upgrade. Check with ISV’s website’s for their plans in regards to CRM 2013.

3. Fixes Issues
It’s very important to record and fix your issues and test them fully before User Acceptance Training (UAT). Errors with the application can quickly kill your user adoption. If you’re not ready, wait! Once the issues have been resolved your ready for testing!

4. Testing your Upgrade
Once you have all the customizations, solutions and errors fixed in your development/test server, you can now perform your User Acceptance Training (UAT) and overall product training. Please note that even with no errors, your users will need training for CRM 2013’s completely redesigned interface.

Make sure you have a strong test plan, allowing users to fully test all of their daily functions. This should also include processes they don’t often run. This should include the Outlook and Web Clients as well as desktop versions Win7/Win8 as well as Office versions (2007/2010/2013) or the combination that is being deployed by your organization.

Once you have signoff, you will want to take the solutions and ISV’s files and you will need to deployment them in the production environment the night of Production Go-Live.

5. Planning your Upgrade
Once you have completed your testing, you can now select to move in your production upgrade date from the CRM Online System. This will allow you to choose the next available date. Once the upgrade starts, you will not be able to access the system for a few hours, and as long as 24 hours.


CRM 2013: Graphical Understanding of the New License Model


We have been fielding a ton of questions in regards to the new Microsoft Dynamics CRM 2013 Licensing Model. I thought it would be helpful to share some licensing details:crmonlinelicensingdetails

So we have three new license types along with new costs.  Specially around costs, lets talk about two great new options INCLUDED with the new cost:

1. Mobility – Microsoft is going to give you mobility licenses for your Windows 8 and IPAD tablets out of the box. Q2 2014 Roadmap shows additional devices for Windows Phone, IPhone and Android devices.
** Note: Android devices might work out of the box, but will not be supported in the first release.

2. Free Instance – Microsoft is providing another free instance for development and test, which will be accessible by all your production user licenses. This is also following best practice to have an environment to develop, test and train in.

Another feature of the new license structure is to give the flexibility for different types of users. This allows the organization the flexibility to pick and choose licensing by user. This also introduces the most amount of questions! 🙂

Here’s the key – If the user is creating Sales Entities (Accounts, Contacts, Opportunities etc.) then they need the Professional License. If the user is a backoffice user only updating (Not creating these records), then they could use the basic license. (UPDATE: it appears creating account and contact records can be handled using the Basic License – Thanks Adam Vero for bring this to my attention). For XRM applications not making use of the main these records types can really benefit from the Essential license to access Customized Entities.

Here’s a great visual chart to determine what each of the licenses provide to help you choose which one. Once upgrade, the customer will be responsible to change the license types in the O365 portal after the upgrade.

crm2013licensebreakdown


CRM 2013: How to enable Bing Maps API integration


Microsoft Dynamics CRM 2013 now comes with an out of the box integration with Bing Maps. This integration uses the address record of your account, contact or system entity to disable that location and render a Bing Map right on the CRM 2013 page.CRM2013accountformwithbing

In order to set this up, you will first need to get a Bing Maps API Key from here:
http://www.microsoft.com/maps/create-a-bing-maps-key.aspx.

You will notice there are several pricing options including a free trial for 90 days. Please decide which one fits your organization best. Now Let’s go Back to CRM to configure it:

Open the Settings, Administration, System Settings. Under the General Tab:bingmapsystemsettings

Select Yes, Show Bing Maps on Forms, and then Insert the Bing Maps API Key in the yellow area. Press save. Now when you open your account, contact or custom entity with Bing Map inserted on the form, you will see the map as shown above!

You can insert the Bing map onto a form by clicking the button for Bing maps on the form customization screen under the insert tab. Please ensure you have address information available on the chosen entity for  your Bing integration. Enjoy!crm2013insertbingmap

Here’s how to do this on a custom entity by my fellow MVP Andrii Butenko
http://a33ik.blogspot.com/2013/10/adding-standard-bing-map-control-to.html

Enjoy