Documentation:String attribute overflowing: Difference between revisions

String attribute overflowing

Latest revision as of 04:57, 12 February 2025

This page was created by Lars.olofsson@mdriven.net on 2022-06-30. Last edited by Stephanie@mdriven.net on 2025-02-12.

If your MDriven Server log contains errors like:

String or binary data would be truncated

You have OCL code, or a part of your system generally puts too-long text into an attribute and then tries to save it.

The rest of the message might be like this:

@errorinfo=S_OutgoingEmail.SS_OutgoingEma... (length=1153) (System.String) (DbType: String)

In this example, the problem is that the serverside email action gets an exception and tries to write that error message to a too-short string attribute.

You have two options, and you should probably use both:

Make the string attribute longer to capture what you want to store
Include code that makes sure you don't overflow the attribute

Use the following OCL to ensure that you never try to write a too-long string:

<attribute>.subString(1,<attribute>.maxLength-1)

For the example above:

self.errorinfo.subString(1,self.errorinfo.maxLength-1)

See also: maxLength

@@ Line 1: / Line 1: @@
-If your MDrivenServer log contains errors like:
+<message>Write the content here to display this box</message>
+If your MDriven Server log contains errors like:
   String or binary data would be truncated
-You have OCL code or a part of your system generally puts too-long text into an attribute and then tries to save it.
+You have OCL code, or a part of your system generally puts too-long text into an attribute and then tries to save it.
 The rest of the message might be like this:
@@ Line 10: / Line 11: @@
 # Make the string attribute longer to capture what you want to store
 # Include code that makes sure you don't overflow the attribute
-Use the following OCL to always ensure that you never try to write a too-long string:
+Use the following OCL to ensure that you never try to write a too-long string:
   <attribute>.subString(1,<attribute>.maxLength-1)
 For the example above:
   self.errorinfo.subString(1,self.errorinfo.maxLength-1)
-See also: [[OCLOperators maxLength|maxLength]]
+'''See also:''' [[Documentation:OCLOperators maxLength|maxLength]]
 [[Category:Error messages]]
+{{Edited|July|12|2025}}