Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The "DynamicEntity XML" code that you create by using the Opportunity form differs from the "DynamicEntity XML" code that you create by using the "Marketing List" form in Microsoft Dynamics CRM 3.0

The "DynamicEntity XML" code that you create by using the Opportunity form differs from the "DynamicEntity XML" code that you create by using the "Marketing List" form in Microsoft Dynamics CRM 3.0

View products that this article applies to.

Symptoms

The DynamicEntity XML code that you create by using the Opportunity form differs from the DynamicEntity XML code that you create by using the Marketing List form in Microsoft Dynamics CRM 3.0. This problem occurs even though you use methods that are documented in the Microsoft Dynamics CRM Software Development Kit (SDK) to capture the DynamicEntity XML that is generated when an opportunity is created in Microsoft Dynamics CRM 3.0.

When the opportunity is created by using by using the Create Opportunity functionality on the Opportunity form, the DynamicEntity XML contains text that resembles the following code example.
<Property xsi:type="CustomerProperty" Name="customerid">
     <Value type="account">{A7DAB4C6-E477-DA11-AD18-000874DE7397}</Value>
</Property>
When the opportunity is created by using the Create Opportunity functionality on the Marketing List form, the DynamicEntity XML contains text that resembles the following code example.
<Property xsi:type="LookupProperty" Name="customerid">
     <Value type="account">{A7DAB4C6-E477-DA11-AD18-000874DE7397}</Value>
</Property>

↑ Back to the top

Cause

This problem occurs because different property types are used for the customerid attribute when the opportunity is created. The LookupProperty property type can be used for many different entities. The LookupProperty property type produces XML that is passed to the Edit.aspx page of the opportunity. This XML resembles the following code example.
<opportunity>
     <name>Opportunity Name</name>
     <pricelevelid type="1022">{F31BB38A-0EC0-403F-99A6-3AF469D7D76E}</pricelevelid>
     <isrevenuesystemcalculated>1</isrevenuesystemcalculated>
     <opportunityratingcode>2</opportunityratingcode>
     <statuscode>1</statuscode>
     <ownerid type="8">{E23750FB-AD71-DA11-AAAA-000D56C2E08A}</ownerid>
     <accountid>{A7DAB4C6-E477-DA11-AD18-000874DE7397}</accountid>
</opportunity>
The CustomerProperty property type is only used for accounts, for contacts, and for leads. The CustomerProperty property type produces XML that is passed to the Edit.aspx page of the opportunity. The XML resembles the following code example:
<opportunity>
     <name>Opportunity Name</name>
     <customerid type="1">{A7DAB4C6-E477-DA11-AD18-000874DE7397}</customerid>
     <pricelevelid type="1022">{F31BB38A-0EC0-403F-99A6-3AF469D7D76E}</pricelevelid>
     <isrevenuesystemcalculated>1</isrevenuesystemcalculated>
     <opportunityratingcode>2</opportunityratingcode>
     <ownerid type="8">{E23750FB-AD71-DA11-AAAA-000D56C2E08A}</ownerid>
     <statuscode>1</statuscode>
</opportunity>

↑ Back to the top

Resolution

This problem is fixed in Microsoft Dynamics CRM 3.0 Update Rollup 1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
922815 Update Rollup 1 for Microsoft Dynamics CRM 3.0 is available
This problem is fixed in Update Rollup 1 for Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935731 Update Rollup 1 for Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers is available

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was corrected in Microsoft Dynamics CRM 3.0 Update Rollup 1 and in Update Rollup 1 for Microsoft Dynamics CRM 3.0 Professional Edition for Service Providers.

↑ Back to the top

More information

For more information about the terminology that is used to describe Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
887283 Microsoft Business Solutions CRM software hotfix and update package naming standards

↑ Back to the top

Keywords: KB915046, kbmbsmigrate, kbqfe, kbbug, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 915046
Revision : 5
Created on : 9/19/2007
Published on : 9/19/2007
Exists online : False
Views : 418