.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-07-02: release Axiell Collections 1.19.1

Today we release Axiell Collections 1.19.1, 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.1, 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.1 should run without problems.

Bug report no.

Short problem description

CV1-6188

Images were incorrectly printed to Word templates: too large and distorted.

CV1-6187

When printing all occurrences of a repeated field group to a table in a Word template, the last occurrence was not printed: instead the first occurrence was printed again.

CV1-6160

When <<[StartRecordList]>> and <<[EndRecordList]>> appeared in an Excel template (which you are not allowed to use in these templates), printing caused an Object not set to an instance of an object error.

CV1-6126

A Bad request error occurred when trying to run an output format with a parameter screen with a single date field configured.

CV1-6119

Auto-complete lists and the Find data for the field term list did not populate for linked fields based on merged link reference fields.

CV1-6100

An Object reference not set to an instant of an object error was produced when adding occurrences in a table grid.

CV1-6093

When Full Text indexing and a reports.inf was implemented, clicking the Create a report... icon generated a 500 server error.

CV1-6092

Users with roles regularly encountered a server error when  using the Hierarchy browser.

CV1-6091

Record type access restrictions set in .inf field properties were ignored.

CV1-6087

The |image|width=nnn parameter in image field references in Word templates ignored any width=%width%&height=%height% parameters set in the image field Retrieval path and always printed full-size.

CV1-6082

There was an error: Something went wrong in the merge process. Text does not end as expected when attempting to export to an .xlsx template if it included fields containing a dot in the field name.

CV1-6077

When the Edit link group on demand screen box setting was enabled, enumerative fields within that group could not load their drop-down list in edit mode. Instead, a constantly spinning wheel appeared.

CV1-6071

Advanced search operators AND and OR would give the same result when searching on internally linked fields.

CV1-6067

When in a Word template a field reference contained an explicit occurrence number higher than 1, then of any following fields without explicit occurrence number, that same occurrence number was being printed (instead of the first occurrence).

CV1-6060

A <<FN|image|width=...>> reference in a Word template did not retrieve an image and <<FN[1].thumbnail|width=...>> would retrieve a smaller than requested thumbnail.

CV1-6048

Linking more than one internally and hierarchically linked record gave a false "Linking this record will result in a circular reference" error.

CV1-6044

For access points (in the Standard search) on linked fields with unique Text indexes or non-unique alpha-numeric indexes in a Full Text indexed database, no terms would show in the Find data for the field window.

CV1-6038

There was a Bad request error after using Clear on non-linked fields in the standard search.

CV1-6036

When a linked field is numerical while it is a text field on screen to get the Find data for the field window to display, then upon selection of a value in that window, a message dialog would display with the text: Error converting nvarchar to numeric. The link would still be made correctly though.

CV1-6034

Copy lists within an occurrence group would always copy from the first occurrence.

CV1-6008

Some searches in Full Text indexes were very slow.

CV1-6004

Removing occurrences from a table grid could, following particular ways of working, result in the wrong occurrence to be removed.

CV1-5923

When using the Favorites feature on enumerative fields, the stored value was the neutral value instead of the user-friendly translation.

CV1-5921

SSO with Multi Tenants was not working if the user belonged to a group that had access to more than one application.