A read-only single line text field of approximately 700k+ characters can prevent records from saving - Support and Troubleshooting

A read-only single line text field of approximately 700k+ characters can prevent records from saving Issue  Symptoms A read-only single line text field containing approximately 700000 characters or more can prevent records from saving.

Steps to reproduce: 1. Log in as administrator. 2. Open the incident form. 3. Add a new Single Line Text field to the form. 4. Open or create an incident record and fill the field with 700k characters or more. 5. Save the record. 6. Set the Single Line Text field to read-only via its dictionary entry. 7. Edit the value of a different field in the incident form. 8. Try to save the record again.

Notice the browser status bar will show "Uploading" for a while and then will fail to refresh the page. Sometimes a new blank record is opened instead, however the record is not saved with the modified values. In the instance log you may see the following error traced: WARNING *** WARNING *** WithTag2 called with no query, returning a new record instead

Release All

Cause When a field on the form has a very large amount of characters, around 700k+ you can encounter the following known issue, PRB604086, every time the form is saved:

"If on incident(or any other form) there is field that is too big and form data in the HTTP request has exceeded the maxPostSize limit of 2MB (default) for Apache Tomcat that form cant be updated or saved."

Resolution The solution is to prevent the the field from having a large amount of data that would cause the HTTP request to reach this limitation. Therefore we recommend the following methods to manage this:

1. Have your user's save large data sets as an attachment rather than on the field 2. If you have users who save on the field, or if the field is being populated by email, you can create a business rule to truncate the data on the field so that it will not exceed a large amount of characters.

Here is an example before business rule which will truncate the description field when a new incident is created and there is over 100k characters:

Name =Truncate large description field Table = Incident Active = true When = before Order = 100 Insert = true

Condition: current.getValue("description").length > 100000

Script:

(function executeRule(current, previous /*null when async*/) {

var truncateMsg = "\n\n**Description has been truncated due to character length being longer than 100,000**"; current.description = current.description.substr(0, 100000) + truncateMsg;

})(current, previous);