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>