Text list has too many characters

Text list has too many characters

We have an application written in 4.6, which has been designed to hold values in text lists. These values are postal codes. The business has changed the way it behaves and has added virtually all the postal codes in the country into one of these fields. We now have errors when trying to save the documents due to the amount of characters in the field. Apart from re-assembling the functionality, is there a workaround?

    Requires Free Membership to View

    Login

    Register today to access targeted resources from our editorial writers and independent industry experts focused on Lotus Domino, Notes, Workplace and other related technologies.

    By submitting your registration information to SearchDomino.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchDomino.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

It's not clear to me whether the document that contains the long list of postal codes is a regular data document, or a reference document that contains the valid values for a keyword field, accessed via @DBLookup.

If the document is a data document, there's not a lot you can do, apart from changing the multi-value text field to a Rich Text field. That will hold all the data you want, but the values will not be available in views and agents. Breaking the field up into multiple multi-value text fields will probably not do any good, because the limit of summary data applies to the document as a whole, not just to each field.

If the document is a reference document, you can break it into two or more documents, each containing a subset of the postal codes and the lookup will still work, provided you don't exceed the limit of 64,000 bytes returned by @DBLookup or @DBColumn.

This was first published in June 2003

Back to top