It seems like the Text field cannot take more than 1000 characters.
Although I can imagine someone reasonably arguing that no-one should need more than 1000 characters for a simple text string
I have found myself writing formulas that generate text strings (including URLs) that are more than 1000 characters.
Can the limit be increased? or is there any workaround?
I was just bitten by this limitation as well.
(Even the User Guide says it should be 5000 characters:
Fibery)
I hit this limitation in Formula field where it’s output is a text field. Specifically a formula that joins all related entity’s public ids in order to check for “contains”. Using this trick: "Contains" formula function - #3 by RonMakesSystems
After there were 300 related entities, this business critical functionality is now broken…
I think i will edit it to use | instead of {} to reduce character count for the time being, but it’s just a problem waiting to show up again…
1000 characters is really quite small when it comes to data amount… it’s like 1kb… Is there any chance to bump this value up to like 10,000 characters? 10kb? I know everything needs some kind of upper limit, heck even rich text fields have an upper limit (2.7mb), but if we could bump this up, at least until there’s a proper “contains” function in formulas, that would be very appreciated!!
are there plans to increase that limit?
for context, I am fetching content from connected pages via JS, string in text fields, and then creating PDF - currently need to split across 16 text fields so that it works (due to hitting length limit in the text field)
probably not very elegant - how else could I accomplish creating one PDF report accumulating data from connected entities?
why you use text fields? why not rich text fields?
tried that
- the script threw “Cannot parse “” entity “” field” with updateEntity on rich text fields (but not on text fields)
- I’m injecting each field’s raw string straight into the HTML template, so plain text is what I want. I need the literal HTML string, not a structured doc. My script builds that HTML by collecting and formatting table views from connected entities, which is why it gets large enough to need splitting.
it does work and the created PDF looks beautiful and custom, but well, split across 16 text fields
You need to read how to update rich text fields - they don’t use updateEntity, they make use of setDocumentContent instead.
There are a few examples here in the community.
Rich text fields will happily take plain text. Although they allow formatting, it’s not mandatory ![]()