Important Note: The CRM Product Group has published a blog titled “Q2 2012 Service Update – New delivery schedule” which clarifies the release plans for upcoming Update Rollups and Quarterly Service Updates in calendar year 2012.
- The release known as the Q2 2012 Service Update will be released in Q4 2012
- i.e. the Q2 and Q4 2012 Service Updates will be combined in the Q4 Service Update
- The CRM Product Group plans to publish a Q4 2012 Service Update Release Preview Guide detailing the new capabilities and interfaces this summer
- An Update Rollup 9 will not be released
- As the Product Group blog mentioned, there will be an Update Rollup 10 released in August, 2012
- Update Rollup 10 will include all hotfixes originally scheduled to be released via Update Rollup 9 and 10
- As Update Rollups are cumulative, Update Rollup 10 will also include all fixes released via Update Rollups 1-8
- Update Rollup 10 will not include new capabilities and interfaces slated for the 2012 Q2 and Q4 Service Releases
- This new functionality will be released via the Q4 2012 Service Update
As you start to plan and think about the upcoming changes to CRM 2011 (http://bit.ly/ur9beta & http://bit.ly/crmr8overview) I suggest familiarizing yourself with the various resources available.
The updated SDK including the changes for UR9 ( http://bit.ly/crm2011sdk ) will be available soon, and that will be a great place to start. Below I’ve referenced content from the “breaking script issues” blog posting (http://bit.ly/MSuCJs) from the CRM product group:
To help guide customers, partners, and ISV’s, the CRM 2011 custom code validation tool has been released to help customers identify and remediate these issues. Here is a link to the validation tool: http://bit.ly/MAtyOh and the blog posting: http://bit.ly/MAtyOZ. The blog article goes into very specific detail around each check item, what they mean, and why each is flagged.
To make sure you’re up to date on these changes please keep following our blog and don’t forget we’re always pushing out information and links as soon as we can via Twitter in between blog postings (@PFEDynamics on Twitter )
Our PFE team members focusing on development are familiar with these changes and have been working with our customers to prepare them for these changes by reviewing unsupported code and putting together remediation plans – and this tool will be yet another way for customers to prepare. Please feel free to let us know if you have any questions.