In CRM, associated views are used to display lists of records when viewing related items within a record. An entity can have more than one associated view. So for example, when viewing activities from within an account, contact and so on, you can choose between the following views:
Microsoft has started releasing some features in CRM as preview features. These are features that are not yet supported but have been made available to get feedback.
If the address on an account record changes, the addresses for any related contacts are not changed. At first it seems that you have to edit each contact record separately which will of course be time consuming. However, a trick I learnt in the early days of CRM is to select the related contacts and then click Edit to open the Edit Multiple Records window where you can type the new address once and update the related contacts (this only works for up to 250 contacts at a time because you are limited to editing one page at a time).
When you create a chart with multiple series, the chart editor insists on adding a secondary y axis scale. This is probably something that you don't want because if you have two or more series comparing similar items the scaling will be different for each series.
There is no way to remove the secondary y axis scale in the editor. However, it can be removed by editing the chart XML. To do this:
One of the Update Rollups for Microsoft Dynamics CRM 2011 stopped multiple line of text fields showing the entire contents when printing. Instead the field is shown as a fixed height window with a scrollbar; which is not particularly helpful when printed.
In CRM 2011, isv.config is not used to store custom buttons, tabs and menus as in earlier versions.
The only item that I think isv.config is used for is to customize the appearance of the service calendar.
When retrieving attributes from linked entities it seems that attributes must have an alias otherwise you can't refer to them:
When faced with the task of creating large numbers of price list items, you may be tempted to use the Import Data Wizard to import and therefore create price list item entries. My advice is don't do this for two reasons:
Dynamics CRM does not provide date only fields. Although date fields may be configured to show the date only, internally the time is stored as well. The time that is stored is usually the time in UTC that corresponds to midnight in the user’s time zone. This may cause date fields to show different values depending on the time zone of the user.