CRM 2013 new form layouts prefers 3 column tabs with 1 column sections over the CRM 2011 1 column tab with 2 column sections. The nice thing about this new layout is that as you resize the browsers window the containing sections will arrange themselves to fit cleanly within the window. This is typical behaviour of floating elements. So for example as you shrink the size of a window a tab with 3 horizontal sections will start to stack on each other vertically. While creating a few custom entities I noticed a slight rendering problem when resizing the CRM’s window. The gap between the final field is a section and the next tab would increase. Take a look at the screen shots below.
While using MSCRM 2011 you might have noticed the customize tab that allows you to alter the current area you are in on the fly providing that you have security rights to do so. What do I mean by on the fly? Well lets say you were creating a record and noticed that a field was in the wrong place. As you have the relevant security rights you decide to make the change there and then. So you go to the customise tab, select form and make the change. This saved you the time of having to go to Settings, Solutions, select your solution, select your entity, select forms, select the correct form etc etc…
While testing importing of several small managed solutions I was able to create what is known as a circular reference in software engineering. Take it from me this is bad! When referencing assemblies in Visual Studio it prevents you from creating the circular references, however in MSCRM 2011 it doesn’t seem to prevent and if it does I managed to create a situation where it allows you to create the circular reference. So for MSCRM 2011 I am going to dub this as a circular dependency. Once the circular dependency was created I couldn’t delete or update either solution because they were dependant on each other!
Recently I posted a tutorial on setting up icons for custom entities. Turns out some of my tutorial was incorrect (Recently corrected)! A friend, Matt Webb was reading through the tutorial and pointed out that MSCRM 2011 no longer uses the 66×48 image size. At first I didn’t believe it, as the help for MSCRM 2011 explained what each icon size is used for. That, along with my previous knowledge on the version 4 icons caused me to go in to denial.
In Microsoft Dynamics CRM 2011 there is a new feature which allows you to add the same field to your form multiple times. However, when customising your form for the first time it is not obvious that you can do this. You wouldn’t know about the feature unless you have read the SDK, release notes or someone’s blog on it! Even some people who know about the feature couldn’t work out how to use the feature straight the way!