Recently, I started a series about certain constraints on exporting or archiving Notes data to PDF. There has been a lot of chatter recently about exporting to PDF, a feature that may be supported natively in HCL Notes V11, and that is offered as an archiving solution by some consultants and vendors.
The PDF format itself is great for certain use cases, but the devil is often in the details. In this case, there are a few details to notice with a document based on a form. A couple are obvious, while another is less obvious. I should note that the date format decision is configurable.
This is the fifth of eight primary issues. When I started the series, I intended to do ten, but decided to combine a few. Just as many issues, but not as many posts so it doesn't get tedious. Depending on what vendor or driver you use, a few of these may have at least a partial solution, but they are good items to check when validating your approach. The table of contents of all issues will be at the bottom of this post.
5) Form data can be difficult to understand
Document based on a simple form (from our CRM database).
PDF rendering, first without notation. See what issues you can find.
Rendered by the Midas LSX to HTML. Compare to the Notes one above.
PDF rendering, now with notations. Three different confusing items
Table of Contents (will be updated as the blog series continues)
Want to try out our Midas LSX export for yourself? Simply fill out the online evaluation request, and we'll get you started. There's no cost to seeing it for yourself.
Copyright © 2019 Genii Software Ltd.
Tags: Lotus Notes PDF Midas LSX HCL Notes Migration Data Loss #DominoForever