We have a scheduled agent running on a Domino 7.0.3 server that takes an email and exports it to dxl. The dxl coming from the server is different from the dxl for the same email if I run the export on the client. The export executes, but when I try to import the files exported on the server I get errors complaining about “refwidth”.<?xml version='1.0'?>
Unknown table element attribute: refwidth
Unknown DXL class library error
DXL importer operation failed
I know I can force this by putting a table in the body and setting the “Use R4 spacing within table” property. But these tables do not have that property as far as I can tell. And if I run the export on the client the dxl output does not contain these refwidth attributes. Any help would be greatly appreciated.
Thanks.
Subject: Problem importing DXL that was exported by a scheduled agent.
So, the client is 6.5.5, the server is 7.0.3? I’m only guessing, because you didn’t state it explicitly.
One more thing you didn’t mention, is your final goal. What are you doing this all for? If DXL export gives different results on 6.5.5 and 7.0.3, you will have no chance but to work around it, as long as both releases are used. Depending on what you need to do with the exported DXL, you could do a simple replace prior to writing the file or apply XSLT transformation, to name two.
Subject: RE: Problem importing DXL that was exported by a scheduled agent.
I have executed the export code from a 6.5.5 client and from a 7.0.2 client. I have also had the code executed by a scheduled agent on 6.5.6 and 7.0.3 servers.
The dxl files created by the clients and the 6.5. server don’t contain a refwidth tag unless the property of the table in the rich text field has the “Use R4 spacing within table” property set. (this is expected and in this case there is also an r4spacing=‘true’ tag)
The dxl generated by the 7.0.3 server always contains a refwidth tag (unless the r4 property is set I believe it should not be there) making it so that I cannot import the dxl afterwards.
The goal is to generate dxl with a scheduled agent running on a 7.0.3 server and have that dxl able to be imported, to reconstitute the document on a 6.5.4 client. (most of our users are 6.5.4) We have been told by a third party software vendor that unless we generate the dxl on at least a 7.0.3 machine that some fidelity will be lost in the resulting dxl. I seem to be finding that there is a problem with the 7.0.3 server specifically. I have even tried using the exporter.DoctypeSYSTEM=“xmlschemas/domino_6_5_6.dtd” while running on the 7.0.3 server to no avail.
Any suggestions?