CRM 2011 – Now works with SQL Server 2012

Microsoft are gearing up for the big new release later this year by releasing SQL Server 2012 and making it compatible with CRM 2011.  The link below goes into detail about the big release

Q2 2012 Service update

So How did I find out about SQL Server 2012 being compatible with CRM 2011, well a couple of sources.

Jamie Miley sums up the changes and has links to the relevant support pages in his blog

http://mileyja.blogspot.com/2012/03/sql-2012-is-now-officially-supported.html

He has some interesting information on a couple of potential problems with the CRM 2011 and SQL Server marriage.

Just be warned, that it’s not perfect yet and Microsoft is working on a couple of issues, but they will have hot-fixes out for these soon.  The issues below are both noted in the KB articles above.

– One issue in 4.0 can cause reports not to be displayed and there isn’t a workaround, but a hotfix is coming.

– Lastly, in CRM 2011, there is still an issue they are working on that can cause the outlook client to fail when using SQL 2012.  A hotfix is also actively being worked on for this at this time also.

I found some information from the excellent blog Dynamics CRM in the field, this is the blog written by Dynamics CRM service team and has some excellent technical information.  Click the link below to find links to SQL Server 2012

http://blogs.msdn.com/b/crminthefield/archive/2012/03/07/dynamics-crm-amp-sql-2012-compatibility.aspx

This blog has some key information in it.

Firstly you need to be on at least rollup 6.

It also has some links to problems which might occur when upgrading to SQL Server 2012 – http://support.microsoft.com/kb/2686619

if you want to know what benefits you will get by using SQL Server 2012 with CRM 2011 then you can read the Microsoft blog below and it will show you the new reporting and other benefits

http://blogs.msdn.com/b/crm/archive/2012/03/07/microsoft-dynamics-crm-and-sql-server-2012-better-together.aspx

Personally I will be waiting until CRM 2011 and SQL Server 2012 has been tested a bit more thoroughly before I consider getting this up and running but releasing this to the CRM community will certainly speed things along.

CRM 2011 – Tool – JavaScript Model Generator

I like to see what useful tools are being created  and there have been some fantastic ones, my favourite is the sitemapeditor

I have been writing some Javascript recently and it’s always a bit of a hassle having to look up all of the  names of the fields you want to use.

In CRM 4 there use to be an excellent tool which created some intellisense for you but I haven’t found anything which is really useful for CRM 2011.

so it is with some interest I saw a tweet from CRM MVP Donna Edwards about a Javascript model generator.  The project is available on codeplex and you can download it using the link below

http://crmjsmodelgenerator.codeplex.com/

Now it took me a while to work out how to get this working, these are the instructions

How to generate it:

NOTE – Make sure your javascript file changes are saved before generating the model as your unsaved changes will get overwritten.

  1. Edit the provided sample.jsconfig file.
  2. Update CrmServer to use the correct server and org.
  3. Set the JsDirectory to be the folder where your script files are located.
  4. Add an Entity node for the entity form that you will be working on
    • EntityName is required and needs to be the schema name
    • FileName is optional and it will try to use the EntityName + “.js” to find the javascript file in the JsDirectory. Use this if the file name is different than the EntityName
  5. Run the JSModelGenerator.exe

<JsConfig CrmServer=”http://server/org&#8221;
JsDirectory=”C:\Source\Project\Scripts”>
<Entities>
<Entity EntityName=”contact” FileName=”contact.js” />
</Entities>
</JsConfig>

I changed the config file but then I was running it and nothing was really happening.  What you have to do is copy specify where the downloaded javascript files are on your computer and then it will update those files and add in the intellisense code to the file.

I quite like this solution because I can now quickly find all the fields on a form and it’s quick and easy to run