Current Issues

10.23

Production numbers can be written to fields that are marked as read only.

10.23

The publisher for Concordance shows as LexisNexis in Windows® Add/Remove Programs option. CloudNine is working to correct this in a future release.

10.21

When using the Field to tag option, it does not apply the last tag name only when the field selected appears after the OCR numbered fields.

Concordance Desktop

10.21

When working with an exported E-Documents database, the drag-and-drop operation for appending new documents causes the near native file import to fail.

Concordance Desktop

10.21

E-Documents import log file lists failed extraction message for a .docx file that does not contain any text and the file is not viewable in Concordance Native Viewer.

Concordance Desktop

10.21

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

Concordance Desktop

10.21

After deleting a record and packing the database, and then attempting to add the document back to the same database using the drag-and-drop operation, produces a message stating that the file already exists.

Concordance Desktop

10.21

When creating an E-Documents database, choosing to map the file path data to a field other than the FILEPATH field does not display the file path as a link in the database.

Concordance Desktop

10.21

Images that are originally set up as "Fit to Width" are not properly processed when imported creating an E-Documents database.

Concordance Desktop

10.21

Data is not imported when the ReadOCR CPL is executed on a text file that contains a single character.

Concordance Desktop

10.21

The PrintPDF.cpl is not included with an E-documents import.  Please contact Concordance Technical Support for a resolution.

Concordance Desktop

10.21

During a Native File Production, a blank text file may be produced if the file name contains any Unicode character.

Concordance Desktop

10.21

The drag-and-drop operation does not work as expected when adding documents to an E-Documents database if the database contains any system fields.  For a resolution, see the System fields improper field rights item in the Information and Error messages topic in the Concordance Answer Center or contact Concordance Technical Support.

Concordance Desktop

10.20

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

Concordance Desktop

10.20

Quick search does not execute a previous search from the quick search list if the query was originally created from the right-click menu in the Tags pane.

10.20

Concordance closes unexpectedly when a user tries to use the Create Query feature in the Notes window.

10.21

10.19

Concordance may stop functioning after applying a quick mark to a transcript and then attempting to export the transcripts database.

Concordance Desktop

10.17

After renaming a table layout in the Table Layout dialog box, all available fields are displayed in the Table view and the new table layout name is not retained.

Concordance Desktop

10.17

Disabling the workspace and then attempting to perform a single database conversion of a Concordance version 9 database may produce an error message and inaccurate data in the database.

Concordance Desktop

10.17

(Windows XP only) When using the Uncheck Issue command in the Tags pane menu for an issue that is applied to multiple notes in a record, an error message may appear and cause Concordance to close unexpectedly.

Concordance Desktop

10.17

When performing a Find and a word is not found, closing the Find dialog box and performing another action may cause Concordance to close unexpectedly.

10.19

10.17

Navigating between documents is slow when working in the Edit view.

10.19

10.16

OPT files exported from a CIB file during a production and contain UTF-8 characters may not import properly into another imagebase.

10.16

Menu items are disabled after setting access limitations even before setting up security for the database.

Concordance Desktop

10.16

When using the Import Wizard to create a database for use with Concordance Native Viewer, importing OCR text and not importing the OPT file, creates an empty CIB file.

Concordance Desktop

10.15

When performing a simple search for Japanese characters (with space between words), search highlights only the first character of the word.

10.17

10.15

Large databases with a large number of records tagged for deletion, may encounter slow performance and a Disk I/O notification during the Pack process.

10.15

During an index process, a message may be displayed indicating that some data is truncated to 64 contiguous characters.  The truncation of data may affect the accuracy for search hits.

10.15

Bulk tagging documents in the same database simultaneously on two separate machines may prompt message and the bulk tagging function will not complete.

10.17

10.15

Retrieving a large number of tags using the Tagsaver.cpl may cause an Insufficient Memory message to appear.

10.16

10.15

(Windows XP) Direct database export from LAW with relative path for text and native files and then running the ImportText.cpt and CreateHyperlinks.cpt point to the wrong location.

10.16

10.15

Tags do not remain on the same records if the database is sorted prior to creating a replica database.  

10.15

Concordance displays the wrong search hits results when performing a consecutive Simple Search using the "with the exact phrase" option after a previous search for two words that are the exactly same and returns zero hits.  

10.16

10.15

Importing E-mails with attachments (.msg file as an attachment) into a Concordance .FYI file, the attached .msg files are saved in the attachment folder of database location.

10.16

10.15

Running a query for multiple tags then creating a replica (without sorting), may bring incomplete tag queries in the replica database.

10.15

Exporting authority lists from the List File Management box, may not export all terms if some of the terms begin with an initial cap and others begin with a lower case letter.  For example:  Anderson, matthews, Johnson, Smith.  The term matthews may not be exported in the authority list.

10.17

10.15

.WK1 and .WK3 formatted files may not be imported into Concordance using the E-Documents or E-mail and Attachments importer.

10.15

.PPTM formatted files may not be imported into Concordance using the E-Documents importer.

10.21

10.13

Concordance may unexpectedly close when scrolling through a new list of values shown in the Edit tab of the List File Management dialog box

10.13

Concordance unexpectedly closes when entering more than 513 characters in a list file on the Edit tab of the List File Management dialog box.

10.13

Search results are not displayed when executing a saved query within the notes.dcb if the saved query was originally created using the Advanced Search pane.

10.13

When tagging records, the Tags pane is not refreshed between query executions when using the Review View and the Split Screen option is disabled.  Refresh occurs when navigating to the next document or performing a right-click action within the Tags pane.

10.20

10.13

A "Dictionary file not found" message is displayed only when using the Advanced Search feature within a Japanese language .FYI type file.

10.13

Selecting the Grayscale option when producing TIFF formatted type files from multi-page native files containing imbedded images, does not render the imbedded images properly.  Use the Color option to produce these types of files.

10.13

Some Kanji characters used in Japanese text are not indexed properly on different operating systems (Windows XP and Windows 7).  

10.15

10.13

(Windows 7 64-bit OS) When running Concordance in conjunction with most document management software and toolbars, the Edit View displays every other field name.  To avoid this situation, when running Concordance, disable these software programs and toolbars.  For additional information, contact the Concordance Technical Support team, email concordancesupport@cloudnine.com, or call (866) 495-2397.

10.17

10.13

Performance may be slow when exporting a Concordance database that contains a complex tag structure.

Concordance Desktop

10.13

Copying data between records using the Copy Previous option in the Ditto dialog box does not copy the contents consistently.

Concordance Desktop

10.13

Email attachments that contain the left curly bracket ({) character a filename may prevent data from importing properly.

10.13

(Concordance versions 10.06 -10.16) When exporting a Security log with a username that contains special characters (ex. %) may cause Concordance to close unexpectedly.

10.13

(Concordance versions 10.12 -10.16) The Security log file does not export properly if a username contains a double-quote (") character.

10.13

Production fails when a header or footer contain the greater than (>) or less than (<) character.

10.13

When producing documents, production numbers are written back to the production number field in the database when a record does not have an associated image.

10.20

10.13

When converting a Concordance version 8.x database to a Concordance 10.x database, if the database contains a tag(s) with the ampersand (&) or pound (#) character in the second character position (i.e. a#Weller) an extra tag is created (i.e. #Weller) in addition to the existing tag.

Concordance Desktop

10.13

When replicating a database, records marked for deletion are not tagged during synchronization if the Append/Restore Deleted records and Tag Deleted Records options are selected.

10.13

Menu access rights are not captured properly when importing a security (CSV) file.

Concordance Desktop

10.13

With the workspace disabled, no message is displayed denying access to the database when attempting to login to a .FYI file after entering a username and no password.

Concordance Desktop

10.13

When working with a concatenated .FYI file, attempts to apply tags to the secondary database in the Table View are not successful.

10.15

10.12

When using the CNV Printing option to print PDF documents to a PDF Distiller or a PostScript printer in Concordance, printouts print inverted (black background and white foreground).  

10.12

An error message is produced when browsing a single record that contains more than 1000 attachments.

10.12

Numeric field data does not appear in full-text search results even though the field is marked to be indexed.

10.12

Opening or creating a database that has a file path exceeding 212 characters causes Concordance to close unexpectedly.

10.12

Using the TRK Maintenance tool in Concordance on a Windows 7 64-bit machine causes Concordance to close unexpectedly.

10.15

10.12

Performing a Synonyms search for a word that begins with a number, returns inaccurate results in Concordance versions 10.12 and earlier. For example, a search for Shupper does not return 5hupper in the Fuzzy Matches list.

10.12

Tags and folders created in the Tag and Issue Management dialog box using Non-ASCII characters, smart quotes, or an em dash causes Concordance to close unexpectedly.

10.13

10.12

When importing E-Documents, the Store File Names option, if selected, becomes cleared when the Browse button is executed to create a log file.  Be sure to reselect the check box before proceeding with the import.

10.17

10.12

When exporting to a Delimited Text File, the Export in ANSI format option, if selected, becomes cleared when the Browse button is executed to create the DAT file.  Be sure to reselect the check box before proceeding with the export.

10.13

10.12

Printing a specific range of pages within a document using the File > Print command within Concordance prints all the pages of the document.

10.13

10.12

When using the CNV Printing option and adding database fields containing rich text formatting with hyperlinks to a header, footer, or watermark, the printed document or image prints the URL not the contents of the URL.

10.12

When multiple database tabs are open, running the Report Writer on any database other than the first database displays all other databases as empty.  To restore the database views close and reopen Concordance.

10.09

Running concurrent opposing bulk tag operations may result in a locked TRK.

10.11

10.09

Running a tag query after packing the database, may result in empty records appearing in the query results for deleted documents that contained the tag.  It is recommended that all tags be removed from records marked for deletion prior to packing the database.

10.09

Running the Reindexing Daemon CPL on a closed database causes the CPL to stop.  

10.13

10.00

HTM files that contain embedded images are not available for viewing from the link in the database record.

10.21

10.00

When selecting specific files to import using the E-Documents import operation and multiple drive tree structures are shown, expanding a single drive tree structure may result in more than one structure expanding.

10.21

10.00

64-bit applications — Concordance 10.08 is a 32-bit application and is not compatible with other 64-bit applications.  For example, Concordance cannot import email files created in Microsoft® Outlook 2010 64-bit.

10.00

HTML encoded files containing non-English text and nested tables may not import into Concordance

10.12

10.00

Concordance 10 and previous versions cannot extract and index text from some embedded HTML tags and malformed HTML tags when imported as E-docs