String length too long went converting lead to opportunity

(0) Share

Report

Posted on by Community Member

I have created a txt field in the lead entity so that I can paste in a WBS that uses a hierachially outline, e.g. 1, 1.1, 1.1.1 . I paste the notes in from a onenote workbook used to qualify a lead (do not want to use dialogs until I am in Opportunity. The issues is that when I attempt the convert the lead to an opportunity, I get the following error (String length too Long)

Here is the actual error catch from the runtime... How can I get around this? Is this related to the 1 to N relationship settings? I want to maintain the content and the formatting when I convert from lead to opp...

Unhandled Exception: System.ServiceModel.FaultException'1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: A validation error occurred. The length of the 'description' attribute of the 'account' entity exceeded the maximum allowed length of '2000'.Detail:

<d2p1:key>CallStack</d2p1:key>

<d2p1:value xmlns:d4p1="http://www.w3.org/2001/XMLSchema" i:type="d4p1:string"> at Microsoft.Crm.Extensibility.VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context)

at Microsoft.Crm.Extensibility.Pipeline.Execute(PipelineExecutionContext context)

at Microsoft.Crm.Extensibility.MessageProcessor.Execute(PipelineExecutionContext context)

at Microsoft.Crm.Extensibility.InternalMessageDispatcher.Execute(PipelineExecutionContext context)

at Microsoft.Crm.Extensibility.ExternalMessageDispatcher.ExecuteInternal(IInProcessOrganizationServiceFactory serviceFactory, IPlatformMessageDispatcherFactory dispatcherFactory, String messageName, String requestName, Int32 primaryObjectTypeCode, Int32 secondaryObjectTypeCode, ParameterCollection fields, CorrelationToken correlationToken, CallerOriginToken originToken, UserAuth userAuth, Guid callerId, Guid transactionContextId, Int32 invocationSource, Nullable'1 requestId, Version endpointVersion)

at Microsoft.Crm.Extensibility.ExternalMessageDispatcher.Execute(IInProcessOrganizationServiceFactory serviceFactory, IPlatformMessageDispatcherFactory dispatcherFactory, String messageName, String requestName, Int32 primaryObjectTypeCode, Int32 secondaryObjectTypeCode, ParameterCollection fields, CorrelationToken correlationToken, CallerOriginToken originToken, UserAuth userAuth, Guid callerId, Guid transactionContextId, Int32 invocationSource, Nullable'1 requestId)

at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType)

at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.Execute(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType)</d2p1:value>

</KeyValuePairOfstringanyType>

</ErrorDetails>

<Message>A validation error occurred. The length of the 'description' attribute of the 'account' entity exceeded the maximum allowed length of '2000'.</Message>

[Microsoft.Crm.ObjectModel: Microsoft.Crm.ObjectModel.TargetAttributeValidationPlugin]

[9223a793-ed74-4280-a1fa-2231e0db9424: TargetAttributeValidationPlugin]

</TraceText>

</OrganizationServiceFault>

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Gus Gonzalez 27,113 on at

Like (0)

Report

The solution is to get rid of the "Single Line of Text" field you have created and create the field as Multiple Lines of Text. The reason behind this is to avoid the 2,000 character limit imposed on Single Line of Text fields.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hmmm. i am almost certain that i created the description field, in both the lead and opportunity entities as multi line, but i will double check...

Was this reply helpful? Yes No
Gus Gonzalez 27,113 on at

Like (0)

Report

If you creaed them as Multi Line of Text then increase the limit from 2,000 to 20,000. That should solve the problem.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Gus thanks so much for your suggestions, but that does not seem to be the case, are you basing your answer on the "Catch error" form the SDK managed code? As I suspected I created the entities as data type "Multiple lines of text" and adjusted the size as I have already run into the issue before. Here is the entity detail for the custom attribute for lead:

And here is is for Opportunity:

To you point the character size is 32K on the opportunity entity, is the MAX 20K and the system does not validate that and perhaps defaults back to 2K? I will try that and if that is the case we have a bug on our hands. But thank again you folks at Zero2Ten have been very helpful to CDW. As a side note, did you see my post for loading the Microsoft Price lists (OB, OV, Select+, EA, EAS, Charity and Online) into the CRM OOB Catalog? Don't you folks do that? Any suggestion re the XML layout to make the import smooth everymonth? And what about the MSSP accelerator? I am sure you folks use that, have you implemented that under CRM 2011 yet? Really want to know how to do a smooth integration with GSX/PSX... Oh my I miss my delivery days doing Biztalk stuff, that made import/export and EAI integration easy. Are you folks using that to integrate with PSX/GSX or ERP?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Looks like this has nothing to do with the opportunity entity and apparently has to do with the "Account Entity". After reading the error catch a little more carefully (Mea culpa i did not do that before, seemed so technical) the error is related to the relationship to the 'account" entity. interesting as i did not create that 1 to 1 relationship so i guess it is OOB. I will check that next week... stay posted for the verified answer, but Gus was on the right track but we where in the wrong entity...

Was this reply helpful? Yes No