‘Field is too large (32k) or view’s column and selection formulas too large’ problem – finally solved!

The internet is full of questions like “I get the message ‘Field is too large (32k) or view’s column and selection formulas too large’ – how do I find and delete the problematic document?”. And there are several attempts to solve this problem, most of them without much chance or quite complicated.

Now I just read the changelog for the new Ytria ScanEZ 12.1 and found this: New scanning method allows easy management for ’32k error’ afflicted documents

I just tested this against a big database of my own and indeed found two documents with summary data of more than 32k. Very nice. Thanks Ytria!


One thought on “‘Field is too large (32k) or view’s column and selection formulas too large’ problem – finally solved!

  1. This has stung us very badly in the past, the most recent one was last week when a new xpage document had a rich text field flagged as issummary for some reason.

    Just for others – if the TOTAL of all of the summary fields in your document is greater than 32k then the document cannot be opened in Notes or XPages.

    Fields need to have doc.issummary = true to be displayed in views or be part of a formula search ( I think )

    In our case we had a lot of configuration fields that did not need to be doc.issummary=true so we programatically change them as each new document is created.

    It did take a while to find as the error message is not that useful.