Sales Order entity error - Text entered exceeds maximum length RRS feed

  • Question

  • We have customized the sales order entity.  We are "cloning" the order to create sales order amendments.  When we try and save the clone record, I get the "The text entered exceeds the maximum length."  If I create a new order with the same data it saves without an issue.

    Any ideas would be welcome.

    Ken Compter
    Friday, February 11, 2011 5:10 PM

All replies

  • Hi Ken,

    When you say you have a 'customized Sales Order Entity' does that mean you customized the existing Sales Order entity or you created a new Custom Entity?  If you are creating a new Custom Sales entity record, then I suspect that one of the fields that you are trying to put data in is not long enough to receive the data.  You'll want to figure out which field that is.  Check all your varchar fields to begin.  Also check any related records that might be getting created as part of the 'cloning' process like Notes, etc.

    If the above does not help, then you can try turning Dev errors on to see if you get a more detailed message about exactly which field is causing the problem.

    It's a little tough to give you anything more specific since this is related to a 'custom cloning method'.

    Regards, Donna

    Friday, February 11, 2011 6:10 PM
  • Thanks for the reply Donna, it is a customization of the SalesOrder entity.  I will re-check nvarchar field lengths, but everything is pretty straight forward.  If it were truely an issue with field length, then I suspect creating a new salesorder would also fail.  I will try Dev errors as next step.

    Thanks again.


    Ken Compter
    Friday, February 11, 2011 7:14 PM
  • Thanks for that information Ken, it helps.

    Just to clarify, you have a Clone button of some sort on a Sales Order and when you select that button (or control) it creates a new Sales Order that is a copy of the current Sales Order, right?  No other records are created right?  No Notes, Activities, Sales Order Product records.......?

    Assuming the above is true, there could be something going on within the plugin itself that is causing the issue and the plugin will need to be debugged.  I don't know what that 'something' is but it is possible that there is something in the code that is causing the exception to the field length, possibly because an attribute related to the Sales Order was modified or some other change to the Sales Order entity. 

    If Dev errors does not help, you can also turn on tracing and look at the trace file.  If that does not help, the next step is to debug the plugin.

    Regards, Donna

    Friday, February 11, 2011 7:58 PM
  • Actually we just created a 1:n relationship to itself (like parent-child cases?) and mapped existing field data to the new record.  Nothing fancy.
    Ken Compter
    Friday, February 11, 2011 8:44 PM