I’m importing a load of dxl into a rich text field to create a table with hotspots and other formatting.
I believe I’ve hit the rich text paragraph limit. The error message is just ‘missing rich text object’, but the import works if I check the length of the dxl string and stop early.
The table I want is about 75,000 characters, but the error comes with a table with even 25,000 characters.
Can anyone suggest another way of doing this, creating a table on the fly with hotspots and table cell colours. The notesrichtexttable doesn’t quite do it, mainly due to the cell backgrounds.
I’m guessing I could split up the table but this would be a last resort.
FYI - a table with 20,000 characters only has about 12 rows in it! It’s got one hotspot on each row and 7 columns in total.
There may well be a DXL limit you are running into, but the limit would not be about tables and numbers of characters. I routinely create rich text tables with two hundred rows (the limit is 255 in Notes), and I routinely create tables using hotspots and cell colors, but I do it with our Midas Rich Text LSX, not with DXL. Nonetheless, it certainly is not a rich text limit, because I can do it manually as well.
How many columns do you have in the table? That could be an issue (the limit is 64). Is there much content in each table cell? Normally, you wouldn’t get close to the limit of paragraphs with only 12 rows in a table, but you could have many paragraphs per cell.
Subject: RE: hitting rich text limit importing dxl
Hi Ben
The table has just 7 columns, will look into whether it’s a dxl limit.
When importing the dxl document that’s created the rich text item is missing from it completely (the document’s still there with a form field and a $Updatedby field).
I have looked at your Midas rich text, but it’s a bit expensive for a small company like us as much as I’d like it and it would solve this problem nicely of course.
The only limit in the DXL Importer is for a composite pool that is used to store the CD records before they get streamed out to items. The current limit would allow for at least a couple hundred 64K items for a single richtext field. (I had never seen this limit exceeded until recently when it happened with a document with 80MB worth of graphics. After increasing a limit [7.03, 8.0] the resulting document produced by the Importer had well over 1000 Body items.) It must be some other problem, most likely a bug rather than a limit.