topic Re: Text Field Value Too Long Despite Being Less than the Field Limit in ArcGIS Online Questions

Text Field Value Too Long Despite Being Less than the Field Limit

cjms — Thu, 21 May 2026 18:31:21 GMT

In ArcGIS Enterprise 11.1, I created a Survey123 form (via the web) that has a multi-line text field question; The app defaults it to 1000 characters. From this hosted feature in Portal, I created a view that I published to AGOL to share with others outside the Org. Process: Hosted Feature Layer View -> Export to temp file gdb -> Publish to AGOL so all fields match

However, despite the field length saying 1000 characters, I only seem to be able to enter 850 characters. If I enter anything more, e.g. if I enter 851 characters, then I receive the error:

Operation failed. The index entry of length 1702 bytes for the index 'exb_event_description' exceeds the maximum length of 1700 bytes for nonclustered indexes.

This is causing an issue in my truncate and append workflow, resulting in a "general function failure" for the append tool.

WARNING 000594: Input feature 120: General function failure.

How can I fix this to allow all 1000 characters to be entered in a 1000 character limit field in AGOL?

Re: Text Field Value Too Long Despite Being Less than the Field Limit

MobiusSnake — Fri, 22 May 2026 05:59:59 GMT

I haven't seen this but it sounds like a database indexing limitation. Did you create an attribute index on that field, and if so, can you drop it?

Re: Text Field Value Too Long Despite Being Less than the Field Limit

cjms — Fri, 22 May 2026 19:03:56 GMT

Yes, when the hosted item was published to AGOL, it defaulted to indices on all fields.

Remove the index from that specific column seems to have fixed the issue. Thanks!

IMO seems a bit strange an index can be created on a field that allows a greater number of bytes than the limit for an indexed field.

Re: Text Field Value Too Long Despite Being Less than the Field Limit

MobiusSnake — Fri, 22 May 2026 19:14:42 GMT

It's very strange you're seeing indexes created on all fields as default behaviour, I only get Object ID, Global ID and edit tracking fields indexed automatically.