Bug report no.

Short problem description

CV1-5953

Possible security issues: some code libraries were not up-to-date.

CV1-5942

An Object reference not set... error occurred when printing to a "raw" printer service.

CV1-5914

The calendar widget behind the Date column Filter option in the Journal maintenance window was too small to display all of its content and it couldn't be enlarged.

CV1-5901

Index on field in hierarchical index linked field group was not updated.

CV1-5899

The Hierarchical internal link type Database scope set to Database still used the Dataset scope.

CV1-5897

When populating a linked field that merges in a mixture of single and multi-occurrence fields (via the linked field mapping), the first occurrence of the grouped fields were merged though, even if they related to a different linked record.

CV1-5895

A pseudonym link reference was not removed when the linked record was deleted.

CV1-5882

There was sometimes a difference in the number of hits displayed in the Result set view and the number of hits displayed for the associated advanced search set.

CV1-5856

Printing with WordCreateDocument generated an error 0.

CV1-5845

People records stored with an empty name.type (do) occurrence had become impossible to modify.

CV1-5842

If a field [E2] was set up to show a list of allowed values from the linked record selected in a field [E1] using the Copy list from linked record functionality and field [E1] was set up using the Repeated, values must be unique configuration, then when attempting to save a record with a duplicate value in [E1] the system would correctly flag the error and not save the record, but when the error message was clicked through, the value in [E2] was removed from the first occurrence.

CV1-5840

$ADMIN features were available to all after update to 1.18.

CV1-5839

There were inconsistent search results for variations of the same Advanced search query.

CV1-5833

In the Record Details > Settings, selecting the Has Data filter mode and clicking OK would only hide screens that are completely empty.

CV1-5816

There was an Object reference not set to an instance of an object exception when creating a use/used-for relation.

CV1-5810

A user that belongs to more than one AD group did not get the access rights of the group in which the user has the most rights.

CV1-5808

Typing data in a table grid field was not possible anymore.

CV1-5769

In a bespoke data source Acquisitions & acquisition proposals, a Standard search on the Object(s) / bulk accessions field would throw an "Invalid column name 'priref'" error.

CV1-5758

Linked metadata fields appeared in the Advanced Search field list as non-indexed fields.

CV1-5750

An indirection search on an indexed link gave an "invalid column name 'term'" error.

CV1-5744

There was an error "The method or operation is not implemented." when attempting to import a certain record into a particular database.

CV1-5743

Printing to a Word template could result in an "Unreadable content found" error when opening the generated document in Word.

CV1-5740

Circular references would freeze Collections.
With the fix, the check for circular links has been improved and now supports multiple levels. When a circular link is detected in a record the following error is shown and Collections no longer freezes: "Linking this record will result in a circular reference."

CV1-5728

An output format did not correctly generate pages for multiple child objects.

CV1-5707

The Related records view did not show (all) references from a linked metadata table field.

CV1-5692

A Word template output format printed HTML codes from HTML field data (instead of interpreting them).

CV1-5679

Export to Excel used full-size images instead of thumbnails when using the webAPI instead of the File system for image retrieval.

CV1-5638

In a Word template, the last fixed word in a cell was printed in the next column.

CV1-5636

Parentheses in a Word template gave unwanted results during printing.

CV1-5635

There was a "Forcing is not allowed" error when trying to update records with a term whose status was candidate, obsolete or rejected, via an import job.

CV1-5617

Penetration tests sometimes reported that security headers were not implemented, but research showed these reports were false positives, so the bug required no action.

CV1-5599

Standard search lists on linked alpha-numerically indexed fields did not respond to search values without zero-padding.

CV1-5566

When a record was copied, then of fields with a default value setting the default value was set in the new record instead of copying the actually present value in the original record (which could be different from the default value).

CV1-5558

Data from previous records was printed in the table of the current record when printing to a Word template.

CV1-5531

Using the ADAPL WordCreateDocument command to create a document with a table containing at least two occurrences of its repeated fields, would give a "Word found unreadable content" warning when opening the document.

CV1-5484

Word template headers were repeated for every record when printing reports.

CV1-5420

Repeated occurrences would overwrite the next row/cell in a table when printing to a Word template.

CV1-5382

Records were wrongly listed as narrower records when exporting multiple records to Word template, but not if only one record was being exported.

CV1-5375

Upload of large files (larger than 4GB) was too slow.

CV1-5286

Printing to label sheets only printed records to the first label column.

CV1-5272

Search-and-replace of a term by a non-preferred term did not replace the non-preferred term by its preferred term.

CV1-5104

The Context string of a multilingual field was not consistently made up out of elements in the current data language.

CV1-5098

It wasn't possible to print to previously uploaded Word templates anymore: the print job would use a different template.