Current Version | Known Issues | Resolved Issues | History

Concordance Desktop - Known Issues

•During production from the new viewer, if any entered free text in the header, footer, margin or watermark sections is the same as one of the database field names, the production will assume the field name has been entered.

•A looping message box bug exists if a user attempts to Find Attachments on a database that has never been indexed. Best practice is index or re-index immediately after creating a new Edocuments or Email database.

•When the Convert to new viewer option is selected, stamp markups placed in the Concordance Desktop Native Viewer version 1.07 or earlier will migrate with the Imagebase, however, they may appear distorted in the new viewer and in printed or produced output.

•When running an image production with existing PageIDs stamped during import of eDocuments or eMail data, unsupported file types that cannot be seen in the viewer are not assigned PageID values and thus will fail to produce with the existing PageID. These records will be listed as an ERROR in the production log.  Data imported from a load file where the image key is a blank value may also exhibit this behavior. You may omit these records from your query for production by searching for BEGNO = “” OR you may provide a unique number for the BEGNO value of these records AND select to Placeholder missing or unsupported file types in the production settings.

•CSV files are not accepted as a load file in the new database import wizard.

•Extracted text for email can include email header information as part of the text.

•For certain Microsoft Office files, the import process for Edocuments and Email may extract dates in the format YYYYMMDD. Searching for dates in text or paragraph fields in these databases should include both MMDDYYYY (MM/DD/YYYY) and YYYYMMDD(YYYY/MM/DD) formats.

•Import of MS Office files (Word, Excel, Power Point, etc.) may fail to extract text from the middle and right header and footer sections.

•In the original Concordance Desktop Viewer, the day of the week (Mon, Tues, Wed, etc.) may be shown incorrectly when a native MSG file is rendered in the viewer. The day of the week is currently rendered in GMT and the date and time are rendered in terms of the time zone set on your workstation.

•Concordance Desktop administrators can avoid the issue by Optimizing MSG files. Optimizing converts the file to PDF for display in the viewer. Please note that optimizing removes all markups including redactions that may have been placed on the record.  

•The "Start" button on the Server tab in the Admin Console is enabled when the CNServer service is running.  Problem occurs only after initial installation.  User will receive a message that the service is running if the start button is clicked.

•If there is a user who's log in name is a shorter version of the another’s name, the user with the shorter name will not be able to open the database once the user with the longer name opens one. For example, if you have two users; the first user's log in name is william and the second user's name is williams, after the second user opens a database, the first user will no longer be able to open it.

•Work-around: To fix the issue, delete the sort layout file.

•When the database SmartPath contains Unicode characters, databases in that folder are still registered. Unicode characters are not support in SmartPath folder names, therefore the databases in the folder should not be registered in Concordance Desktop.

•When importing documents with Right-To-Left (RTL) languages, such as Arabic, the imported text may be incorrectly justified to the left side.

•If more than one user runs a Tally after a query on a tag is run, Concordance stops running for the user who started the first Tally.

•Graphs create in PowerPoint 2013 are not rendered on near native in e-document databases.

•Markup types, with a status of "no" are included with printing from the Concordance Desktop viewer.

•Changing or renaming media keys prevents Concordance from executing a Native File production; however, the documents are still displayed in Concordance Native Viewer.

•Header and footer information is not captured in the text of a record and is not imported for Microsoft® Word documents when performing an E-documents import.

•Databases that contain more than 100 matters, clients, and users and have an underscore (_) character within the matter or database name, displays a duplicate matter or database on the Tree tab.

•When Microsoft Excel 2013 is installed and Send to Excel is selected, a blank Excel workbook is opened.

•Unable to run a native file production for all native files in a database by selecting an Image Key, when the database is in a concatenated set.