Notes/Domino Fix List
![](/ldd/fixlist.nsf/10x10.gif?OpenImageResource) | ![](/ldd/fixlist.nsf/lot_swlogo_104.gif?OpenImageResource) |
SPR # JSHN6N3QY8 | Fixed in 6.5.6; 7.0.3 release | Regression in 6.5.5 |
![](/ldd/fixlist.nsf/10x10.gif?OpenImageResource)
![](/ldd/fixlist.nsf/thread-divider.gif?OpenImageResource)
![](/ldd/fixlist.nsf/10x10.gif?OpenImageResource)
Product Area: Client Technical Area: Client UI Platform: Cross Platform
Lotus Customer Support APAR: LO13414
![](/ldd/fixlist.nsf/10x10.gif?OpenImageResource)
SPR# JSHN6N3QY8 - Prior to this fix, hidden tables were exposed when exporting to a Microsoft RTF document using @Command([FileExport];"Microsoft RTF";filepath). With this fix, Notes doesn't export the invisible tables.
![](/ldd/fixlist.nsf/10x10.gif?OpenImageResource)
Technote Number: 1233175
![](/ldd/fixlist.nsf/10x10.gif?OpenImageResource)
Problem:
This issue has been reported to Quality Engineering as SPR# JSHN6N3QY8 and has
been fixed in Notes/Domino 6.5.6.
Excerpt from the Lotus Notes and Domino Release 6.5.6 MR fix list (available at
http://www.ibm.com/developerworks/lotus):
Client UI
SPR# JSHN6N3QY8 - Prior to this fix, hidden tables were exposed when exporting
to a Microsoft RTF document using @Command([FileExport];"Microsoft
RTF";filepath). With this fix, Notes doesn't export the invisible tables.
Workarounds
The issue does not occur if you open the document and manually export the
document. The export dialog can be initiated either using the menu option File
-> Export, or using the @Command FileExport with no parameters:
@Command([FileExport])
If a fully automated workaround is desired then this can be accomplished for
cases where the table is part of the form. The workaround requires moving the
table design element into a subform. In the form a computed subform design
element is then used to reference the subform containing the table. The
computed subform formula can be designed to only include the subform if an
environment variable in the Notes.ini is set to a particular value. The
formula which executes the @Command FileExport will need to include code to set
the environment variable to the values which will result in the subform being
included or not.
For example:
The following formula would be used for the computed subform formula within the
form.
@If(@Environment("table1export")="show";"SubformWithTable";"")
Note: "SubformWithTable" is the name of the subform that contains the table.
The export formula would set the environment variable "table1export" to "hide",
perform the export, and then reset the variable to "show":
@SetEnvironment("table1export"; "hide");
@Command([FileExport]; "Microsoft RTF"; "C:\\data\\export1.rtf");
@SetEnvironment("table1export"; "show")
More >
![](/ldd/fixlist.nsf/10x10.gif?OpenImageResource)
![](/ldd/fixlist.nsf/10x10.gif?OpenImageResource)
Last Modified on 12/08/2013
Go back
![](/ldd/fixlist.nsf/10x10.gif?OpenImageResource) |