During the order assetization process, you might encounter a runtime (RTEL) failure with the following error message:
data value too large: (max length=40)
This error occurs because of a data length mismatch between upstream objects and the downstream Asset State Period object:
QuoteLineItem.SegmentName - Text(255)
OrderItem.SegmentName - Text(255)
AssetStatePeriod.SegmentName - Text(40)
When a ramp product is added to a quote line item with a segment group name exceeding 40 characters (for example: Order Year 3 : 7 November 2025 to - Amend), that value flows downstream. During assetization, the system attempts to write this value to AssetStatePeriod.SegmentName. Because the platform doesn't automatically truncate the text or handle the validation gracefully, the process fails.
During the amendment process, the platform automatically appends Amend to the existing SegmentName each time a new Asset State Period is created. This repeated concatenation causes the string to grow with each subsequent amendment, making it likely to eventually exceed the 40-character limit even if your original name was short.
Salesforce has confirmed this field length mismatch is a platform bug rather than a configuration error.
Salesforce Engineering is tracking this issue via bug W-21878474. A permanent fix is scheduled to update AssetStatePeriod.SegmentName (along with SegmentId and RampId) to Text(255) to align the field lengths end-to-end.
To track the status of this deployment, view the official Salesforce Known Issue page.
Note: This upcoming platform fix only increases the field character limit. It won't stop the system from repeatedly appending
- Amendduring amendments.
If you are experiencing this error before the platform fix is active in your org, implement the following two-part customization:
Enforce character limits upstream: Create a validation rule on the QuoteLineItem or OrderItem object to ensure the SegmentName field does not exceed 40 characters before the order is activated.
Control the amendment naming pattern: Implement automation (such as a Flow) to intercept the repeated appending of - Amend. Replace it with a structured, controlled pattern (such as - Amendment 1, - Amendment 2) to keep character counts predictable.
005385763

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.