Thursday 27 June 2013

MSCRM 2011 - Next Update ....... Changes in the Next Major Release


Below contents are taken from msdn.


Removal of the 2007 Endpoint and Legacy Features


The 2007 service endpoint was deprecated in the Microsoft Dynamics CRM 2011 release. Extensions that use the 2007 endpoint will not be supported and will not work in the next major release of Microsoft Dynamics CRM. Note the following more detailed information: 

Microsoft Dynamics CRM Online customers using the Microsoft account identity provider can continue to use extensions that require the 2007 endpoint after upgrade. However, prior to the transition of your organization to Microsoft online services (MOS), you will need to upgrade or remove those extensions that require the 2007 endpoint. 

  • Microsoft Dynamics CRM Online customers using the Microsoft online services (MOS) identity provider will see no change in service. The 2007 endpoint has not been supported in organizations using the MOS identity provider.

  • When Microsoft Dynamics CRM 2011 on-premises and IFD customers try to upgrade their server to the next major release of Microsoft Dynamics CRM, the upgrade process will detect extensions that are using the 2007 endpoint or legacy Microsoft Dynamics CRM 4.0 features. If any of these extensions are found, the Environmental Diagnostic Wizard will report an error and you will not be able to continue the upgrade until those extensions are removed or upgraded to use the 2011 endpoint.   

The following legacy Microsoft Dynamics CRM 4.0 features will be removed or will no longer be supported in the next major product release:

Ø  CRM 4.0 ISV folder support for custom web applications

Ø  Microsoft Dynamics CRM 4.0 plug-ins

Ø  Microsoft Dynamics client-side scripting

Ø  Microsoft Dynamics CRM 4.0 custom workflow activities

In addition, the Solution Down Level tool will be removed from the Bin folder of the SDK package and no longer be available. Due to improvements to the solution framework this tool is no longer needed.

Removal of JavaScript Form Scripting Support for Microsoft Dynamics CRM 4.0 Objects and Functions

Microsoft Dynamics CRM 4.0 exposed global functions and form objects to form scripting with JavaScript. These scripting objects and functions were deprecated in the Microsoft Dynamics CRM 2011 release and will be removed in the next major release. All form scripts for the next release should use the Xrm.Page and Xrm.Utility object models.
Changes to the Document Object Model (DOM)

The next release of Microsoft Dynamics CRM will make many changes in the Document Object Model (DOM). Writing JavaScript code that modifies the DOM is not supported and you should expect that any scripts written using Microsoft Dynamics CRM application page DOM elements will break.

Removal of Some Ribbon Controls

The following ribbon controls are no longer supported and will not work in the next major release:

<ColorPicker> (RibbonDiffXml)

<ComboBox> (RibbonDiffXml)

<DropDown> (RibbonDiffXml)

If you have used the DropDown control you should convert it to use the FlyoutAnchor control instead.

<Gallery> (RibbonDiffXml)

<GalleryButton> (RibbonDiffXml)

<InsertTable> (RibbonDiffXml)

<MRUSplitButton> (RibbonDiffXml)

If you have used the MRUSplitButton control you should convert it to use the SplitButton control instead.

<TextBox> (RibbonDiffXml)  

Microsoft Lync Presence Not Supported

Microsoft Lync presence will not be supported on the updated user interface entity forms and in Activity Feeds. Lync will be present in grids and subgrids

Removal of Workplace and Personalization Options for New Customers

In the next release the Workplace area in the navigation will not be present at all for new organizations. However, organizations upgrading from Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online will retain their existing workplace areas but users will no longer have the option to personalize what is displayed there within the Personal Options. Whatever personal option settings people had at the time of the upgrade will persist. The <Group> (SiteMap)IsProfile attribute will no longer allow groups to be options that users can select to include in the workplace.

Duplicate Detection during Record Create and Update Operations Not Supported

Duplicate detection during create and update operations will not be supported for Microsoft Dynamics CRM updated user interface entities. Duplicate detection of individual records won’t be supported for custom entities as well. However, to detect duplicates in bulk, you can use the BulkDetectDuplicatesRequest message and the RetrieveDuplicatesRequest message..

The following table contains a list of the updated user interface entities available in the next major release of Microsoft Dynamics CRM. These entities will not have duplicate detection support during record create or update operations:


Schema Name Display Name 
AccountAccount
AppointmentAppointment
CampaignCampaign
CampaignActivityCampaign Activity
CampaignResponseCampaign Response
CompetitorCompetitor
ContactContact
EmailEmail
FaxFax
IncidentCase
InvoiceInvoice
LeadLead
LetterLetter
ListMarketing List
OpportunityOpportunity
OpportunityProductOpportunity Product
PhoneCallPhone Call
ProductProduct
ProductPriceLevelPrice List Item
QuoteQuote
RecurringAppointmentMasterRecurring Appointment
SalesLiteratureSales Literature
SalesOrderOrder
SystemUserUser
TaskTask
TeamTeam

No comments:

Post a Comment