Mapping from Version 1.2
Generally, Microsoft CRM 3.0 SDK is backward compatible with earlier versions. This means that you can include the old DLLs from the earlier version and your code will still work using the old programming style. There are some exceptions:
- Activities. CRMActivity and CRMEmail proxy objects are not supported. Code written against these objects must be converted to the new programming model.
- Methods that create activities. This includes CRMSalesOrder.Cancel, CRMOpportunity.Lose, and CRMIncident.Close.
- Workflow. The CRMProcess proxy object is no longer supported. It is recommended that all workflows be created by using the Workflow Manager.
- Rich Client Sync. Use of the CRMRichClientSync proxy object is no longer supported.
- CRMCustomization. This class is no longer supported. To transform entity instances, use the InitializeFrom message.
- CRMSalesperson. This entity is no longer supported. Use systemuser instead.
- CRMAnswer. This entity is no longer supported.
- Teams security. Teams cannot own objects in Microsoft CRM 3.0.
- MakePrivate/MakePublic. These methods are no longer supported.
- Organization. The organization entity does not support Create, Delete, Enable, and Disable actions.
- Client Side Scripting. Syntax differences between version 1.2 and Microsoft CRM 3.0 may cause client-side script failures after upgrade. For more information, see Client Side Scripting.
- Upload Attachment SRF Files. In Microsoft CRM version 3.0 the attachment SRF files have been removed. The version 1.2 methods for uploading and downloading attachments have been deprecated. You should use the UploadFromBase64 messages to upload attachments. See UploadFromBase64DataActivityMimeAttachment, UploadFromBase64DataAnnotation and UploadFromBase64DataSalesLiteratureItem.
Warning Microsoft CRM V1.x APIs located in the assemblies Microsoft.Crm.Platform.Proxy, Microsoft.Crm.Platform.Types and http://<server name>/mscrmservices/*.srf are deprecated and are considered obsolete. This means that these APIs may not be supported in future versions of Microsoft CRM. You should avoid the use of Microsoft CRM V1.X APIs and you are strongly encouraged to migrate and develop your applications by using the Web services that are described in this version of the Microsoft CRM 3.0 SDK and the accompanying documentation.
In This Topic
The following table shows the mapping of the proxy object name from Microsoft CRM V1.2 to the entity name in Microsoft CRM 3.0.
© 2007 Microsoft Corporation. All rights reserved.