Microsoft Dynamics CRM

CRM 2015 Deprecated MESSAGES

There is very good documentation available for deprecated client side code, but very less on deprecated server side messages.

Here is a helpful list:

CRM 2015 messages which are deprecated:

Class
Description
AddProductToKitRequest Deprecated. Use the ProductAssociation entity. Contains the data that is needed to add a product to a kit.
AddProductToKitResponse Deprecated. Use the ProductAssociation entity. Contains the response from the AddProductToKitRequest class.
AddSubstituteProductRequest Deprecated. Use the AssociateRequest class. Adds a link between two entity instances in a many-to-many relationship.
AddSubstituteProductResponse Deprecated. Use the AssociateRequest class and its associated response class. Contains the response from the AddSubstituteProductRequest class.
AssociateEntitiesRequest Deprecated. Use the AssociateRequest class. Contains the data that is needed to add a link between two entity instances in a many-to-many relationship.
AssociateEntitiesResponse Deprecated. Use the AssociateRequest class and its associated response class. Contains the response from the AssociateEntitiesRequest class.
CompoundCreateRequest Deprecated. Use the CreateRequest class. Creates a compound entity, such as a sales order (order), invoice, quote, or duplicate rule (duplicate detection rule); and its related entity, such as a sales order detail (order product), invoice detail (invoice product), quote detail (quote product), or duplicate rule condition.
CompoundCreateResponse Deprecated. Use the CreateRequest class and its associated response class.
CompoundUpdateRequest Deprecated. Use the CreateRequest class. Contains the data that is needed to update a compound record, such as a sales order (order), invoice, quote, or duplicate rule (duplicate detection rule); and its related detail record, such as a sales order detail (order product), invoice detail (invoice product), quote detail (quote product), or duplicate rule condition.
CompoundUpdateResponse Deprecated. Use the CreateRequest class and its associated response class. Contains the response from the CompoundUpdateRequest class.
ConvertKitToProductRequest Deprecated. Contains the data that is needed to convert a kit to a product.
ConvertKitToProductResponse Deprecated. Contains the response from the ConvertKitToProductRequest class.
ConvertProductToKitRequest Deprecated. Contains the data that is needed to convert a product to a kit.
ConvertProductToKitResponse Deprecated. Contains the response from the ConvertProductToKitRequest class.
DisassociateEntitiesRequest Deprecated. Use the DisassociateRequest class. Contains the data that is needed to remove a link between two entity instances in a many-to-many relationship.
DisassociateEntitiesResponse Deprecated. Use the DisassociateRequest class and its associated response class. Contains the response from the DisassociateEntitiesRequest class.
ExecuteFetchRequest Deprecated. Use the RetrieveMultipleRequest class.
ExecuteFetchResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class.
IsBackOfficeInstalledRequest Deprecated. Checks whether Microsoft Dynamics GP 9.0 is installed.
IsBackOfficeInstalledResponse Deprecated.
MakeAvailableToOrganizationReportRequest Deprecated. Use the UpdateRequest class.
MakeAvailableToOrganizationReportResponse Deprecated. Use the UpdateRequest class and its associated response class.
MakeAvailableToOrganizationTemplateRequest Deprecated. Use the UpdateRequest class.
MakeAvailableToOrganizationTemplateResponse Deprecated. Use the UpdateRequest class and its associated response class.
MakeUnavailableToOrganizationReportRequest Deprecated. Use the UpdateRequest class.
MakeUnavailableToOrganizationReportResponse Deprecated. Use the UpdateRequest class and its associated response class.
MakeUnavailableToOrganizationTemplateRequest Deprecated. Use the UpdateRequest class.
MakeUnavailableToOrganizationTemplateResponse Deprecated. Use the UpdateRequest class and its associated response class.
RemoveProductFromKitRequest Deprecated. Use the ProductAssociation entity. Contains the data that is needed to remove a product from a kit.
RemoveProductFromKitResponse Deprecated. Use the ProductAssociation entity. Contains the response from the RemoveProductFromKitRequest.
RemoveSubstituteProductRequest Deprecated. Use the ProductSubstitute entity.
RemoveSubstituteProductResponse Deprecated. Use the ProductSubstitute entity.
RetrieveMembersTeamRequest Deprecated. Use the RetrieveMultipleRequest class.
RetrieveMembersTeamResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class. Contains the response from the RetrieveMembersTeamRequest class.
RetrieveSubsidiaryTeamsBusinessUnitRequest Deprecated. Use the RetrieveMultipleRequest class.Contains the data needed to retrieve a collection of entity instances based on the specified query criteria.
RetrieveSubsidiaryTeamsBusinessUnitResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class.
RetrieveSubsidiaryUsersBusinessUnitRequest Deprecated. Use the RetrieveMultipleRequest class.Contains the data needed to retrieve all user information from the child business units of the specified business unit.
RetrieveSubsidiaryUsersBusinessUnitResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class.Contains the response from the RetrieveSubsidiaryUsersBusinessUnitRequest message.
RetrieveTeamsSystemUserRequest Deprecated. Use the RetrieveMultipleRequest class.Contains the data needed to retrieve the list of teams of which the specified user is a member.
RetrieveTeamsSystemUserResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class.Contains the response from the RetrieveTeamsSystemUserRequest message.
RetrieveUserSettingsSystemUserRequest Deprecated. Use the RetrieveMultipleRequest class.Contains the data needed to retrieve the user settings for the specified system user (user).
RetrieveUserSettingsSystemUserResponse Deprecated. Use the RetrieveMultipleRequest class and its associated response class.
UpdateUserSettingsSystemUserRequest Deprecated. Use the UpdateRequest class.
UpdateUserSettingsSystemUserResponse Deprecated. Use the UpdateRequest class and its associated response class.

 

Hope it helps!

Advertisements

5 thoughts on “CRM 2015 Deprecated MESSAGES”

      1. actually i will put in the comments here:

        Source for CRM 2013 and CRM 2015: https://msdn.microsoft.com/en-us/library/gg509046%28v=crm.6%29.aspx

        Deprecated features removed in this release
        The following features frequently used in form scripts were deprecated in Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online and are not available in Microsoft Dynamics CRM 2013 and Microsoft Dynamics CRM Online:
        Microsoft Dynamics CRM 4.0 object model
        The objects described in the Microsoft Dynamics CRM 4.0 SDK topics Form Programming Reference and Global Scripting Reference are no longer available. Each global function or variable has been replaced with a new API. See Client-side context (client-side reference)for the APIs that replace them. Any code that references the crmForm object must be replaced with equivalent APIs that are included in the Xrm.Page object. More information: Client-side programming reference and Form scripting quick reference
        Microsoft Dynamics CRM 4.0 (2007) web service endpoint
        The Microsoft Dynamics CRM 4.0 SDK included some sample code in Scripting Sample Code that described how to access data using the 2007 web service endpoint using JavaScript. However, since Microsoft Dynamics CRM 2011 was released, the preferred methods to access web services have been to use the OData (REST) endpoint and the Modern App SOAP endpoint. Because the 2007 endpoint is removed in this release, you must update your code to use either the OData or Modern App SOAP endpoint. More information: Use web service data in web resources (OData and Modern app SOAP endpoint)
        Xrm.Page.context.getServerUrl and Xrm.Page.context.AuthenticationHeader
        Xrm.Page.context.getServerUrl was deprecated in favor of Xrm.Page.context.getClientUrl to provide a consistent method to get the organization URL.
        Xrm.Page.context.AuthenticationHeader was never needed for the OData (REST) endpoint or the Modern App SOAP endpoint. It was only provided to provide an alternative to the Microsoft Dynamics CRM 4.0 GenerateAuthenticationHeader Function. Now that the 2007 endpoint is removed there is no need for it.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s