Notes/Domino Fix List
 |  |
| SPR # CSMH6N6QBR | Fixed in 7.0.3; 6.5.6 release | Regression in 6.5.5 |
Product Area: Client Technical Area: Client UI Platform: Cross Platform
Lotus Customer Support APAR: LO13501
SPR# CSMH6N6QBR - Fixed an issue that prevented folders with the same name in different parent folders, from displaying in the mail navigator.
Technote Number: 1239383
Problem:
This issue was reported to Quality Engineering and has been fixed in Domino
release 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# CSMH6N6QBR - Fixed an issue that prevented folders with the same name in
different parent folders, from displaying in the mail navigator.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Workarounds:
Rename existing folder names to more unique names at the lower or upper level.
It may not be necessary to rename all of the folders; renaming only some of
them may actually resolve the issue.
Another alternative is to restructure the folder levels so that the subfolder
becomes a folder. For example, if you had an East Coast\Sales folder structure
you could rename the Sales folder to East Coast Sales, and then move it up to
the folder level so that it is no longer a subfolder of East Coast. To rename a
folder, use the Rename menu option. To move a folder, use the Move option.
Note: To move a folder so it is not a subfolder, select the entry "-Folders-"
in the Move folder dialog.
For cases where there are many repetitive folder name structures, another
workaround is to use a categorized view. For example, if you have folder
structures similar to Company\Orders\Part\Qtr Year and
Company\Shipped\Part\Qtr Year etc, you could create a categorized view, and
base its column values on field values for each of the relative items.
Additional Information
A cumulative client hotfix (CCH) is available for Notes client 7.0.2 and 6.5.5
that fixes the issue reported in SPR# CSMH6N6QBR. Since hotfixes do not
receive the extensive testing that maintenance releases and fix packs do,
customers are encouraged to implement workarounds or deploy a release
containing the fix once available. However, if workarounds are not possible or
applicable and you still need a fix, contact IBM Technical Support to request
the CCH containing the fix for this issue. More >
Last Modified on 06/17/2016
Go back
|