Rich text object is invalid with NotesDXLImporter.process

Apparently I’ve got invalid Rich Text in a document. I need a way to validate the rich text and to identify problems.

I’ve got one script that exports a document and another script that imports a document. Nothing is done to the exported document, this is just a way to store a document outside of Notes in the file system. Usually it works.

With some very large docs I get “Rich text object is invalid” reported by the importer.log and a final message “DXL importer operation failed”

Because it usually works, I assume the problem is with the data. But it was a valid document before exporting. And I have no way to determine what is wrong with the Rich Text in the document.

Any way to validate the Rich Text in a document prior to exporting it? Any way to pinpoint exactly what is wrong with the Rich Text?

Subject: Rich text object is invalid with NotesDXLImporter.process

More info on this problem: The “invalid rich text” has doclinks. When the doclinks are removed, NotesDXLImporter.process successfully completes.

So, next question: Why can’t NotesDXLImporter handle a doclink?

Subject: RE: Rich text object is invalid with NotesDXLImporter.process

Hi Mark, the same issue in my agent. After 2hours of playing with the DXL file my conclusion is: It’s a bug in parsing ‘description’ attribute of element. It is possible to have only 209 characters inside that attribute on my R6.5.4. With 210 or more the DXLImporter fails. Strange…

I’ll try it on R7 later this week and keep you posted.

Bye,

Tom.

Subject: It’s fixed in R7

Mark, it works fine on R7.0 Gold.

The ‘description’ attribute of element remains limited in length. If you have it longer than the limit, the DXLImporter trims it but does NOT crash.

Bye,

Tom.