.NET Framework 4.8 required

The Microsoft .NET Framework Runtime version 4.8 must be installed on the IIS server running Collections (after which the server needs to be rebooted). Ask your system administrator if this still needs to be done.

New options and functions for Axiell Collections make further use of Adlib for Windows impossible

Some of the new functionality introduced in this version and previous versions of Collections requires to be set up by your application manager (as indicated per topic in the various Collections release notes), using new options in Axiell Designer. Since development of Adlib for Windows has ceased quite a long time ago, these new options are not supported by Adlib for Windows. Even if Adlib would ignore the relevant option, you could no longer reliably work in Adlib too, so altered applications using Collections-only functionality should never be opened in Adlib again.

New Collections online Help

The current English version of the Collections online Help you see before you, has been revamped and moved to a different URL: http://help.collections.axiell.com/. To have your Collections application open that new version automatically, your application manager will have to make a simple change to the Collections settings.xml file: almost at the top of that file, the <Help>http://documentation.axiell.com/alm/collections/</Help> reference (which points to the current version) should then be replaced by <Help>http://help.collections.axiell.com/</Help>. After recycling the application pool, clicking the Help button in the main toolbar on the left, will open the new Help version if you're connected to the internet.
Note that the new version will only be present in English for now. If you make the change above and you click the Help button, you will always be redirected to that English version, regardless of the interface language currently active in Collections. Since the current Collections online Help is available in Danish and French too, users in those language regions are probably better off leaving the <Help> setting as it is, as this will still allow you to use the Help in your own language.

2024-04-16: release Axiell Collections 1.19

Today we release Axiell Collections 1.19, offering the bug fixes described below.

A possible issue on Windows 2022 Server only (depending on what other software already has been installed on it) is that after installing Collections 1.19, when trying to run Collections, you’ll get an “Error loading SqlServerSpatial160.dll (ErrorCode: 126)” error. This just means that the latest Microsoft Visual C++ Redistributable Version is not yet present on your server. Just install it from https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170: select the proper executable for your architecture (so e.g. https://aka.ms/vs/17/release/vc_redist.x64.exe for X64) and install it. After that, Collections 1.19 should run without problems.

Bug report no.

Short problem description


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


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


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.


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


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


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.


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


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.


Printing with WordCreateDocument generated an error 0.


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


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.


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


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


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


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


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.


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


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.


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


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


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


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


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."


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


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


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


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


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


Parentheses in a Word template gave unwanted results during printing.


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.


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


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


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).


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


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.


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


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


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


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


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


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


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


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