Update Rollup 13 was released last week. This update provides long-awaited support for Windows Server 2012 as well as support for ADFS 2.1.
To install CRM 2011 on Windows Server 2012, a setup update is required first which won’t be available until April 9th. http://technet.microsoft.com/en-us/library/dn167638.aspx
SDK v5.0.15
A new version of the SDK was also released last week and it provides new DLLs that are compatible with both UR 13 and CRM Online. A new version of the Metadata Browser t adds new properties from UR 12.
Important new design considerations were added to the SDK for the new Auto Save feature in CRM Online . Microsoft explains that the reason for moving to an auto save is to keep consistency with modern applications and that it can’t be disabled or configured- this could be an abrupt change for users who have been using CRM for a while.
A very important note to customizers and developers explains that each auto save is considered an update so: workflows, plug-ins and auditing will trigger each time. The filtering attributes in plug-ins and workflows will be even more important so that those trigger only when specific fields are updated.
The following excerpt was taken from this page in the SDK – http://msdn.microsoft.com/en-us/library/hh913610.aspx.
Modern applications are moving to an implicit save model. The updated forms introduce this behavior in Microsoft Dynamics CRM Online. Auto save is not configurable. You cannot disable it or change the behavior. There is no save button. The auto save control appears in the bottom right area of the updated form and has the following behaviors:
When creating a new record there is a Create button in the command bar.
Auto save does not apply until the record is created.
After the first edit of the form, auto save occurs every 30 seconds.
Auto save retrieves any changes to the record and displays them without reloading the form.
Only data that has been changed since the last save are saved.
The field currently being edited is not saved.
Command bar actions like New, Close, or Qualify saves the record.
Closing the form saves the record.
Note
Each time auto save occurs, it is considered an update to the record. Plug-ins, workflows, and auditing of records will treat each update as a separate event. Developers and creators of workflows need to consider the impact this will have on the business logic included in their plug-ins and workflows. Rather than triggering business logic on each update, you should include conditions to check the values of specific fields in the update to initiate your logic so that they won’t occur indiscriminately with each update.
