Notes de version 1.19.2
Contents
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-08-30: release Axiell Collections 1.19.2
Today we release Axiell Collections 1.19.2, 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.2, 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.2 should run without problems.
Bug report no. |
Short problem description |
CV1-6274 |
Certain incorreclty designed Word templates could stop processing on certain records and Collections would stall. |
CV1-6267 |
Indexed links could cause data loss after executing the Change location task. |
CV1-6262 |
Where an indexed link plus metadata existed between loan item and loans, when a loan item was created and it was linked to the loan and the metadata fields were updated, you could see the data correctly in the loan item, but the loan seemed to be unchanged. |
CV1-6259 |
In a specific application, a The multi-part identifier "collect.priref" could not be bound error appeared when doing a search without search key. |
CV1-6257 |
In certain setups, tecord level security was no longer enforced. |
CV1-6246 |
When retrieving records from external sources, linked fields were not resolved and enumerative fields not normalised to the neutral value, resulting in data loss from retrieved records. |
CV1-6237 |
Nested indirection searches like acquisition_item -> (acquisition -> method=gift) failed for indexed linked fields. |
CV1-6235 |
The Secrets store utility was unable to list all secrets and you couldn't add a secret after the first secret was set. |
CV1-6228 |
No related records were visible in the Related records view for records in which a priref field with content was present (priref fields are not allowed in record content, only in record headers). |
CV1-6213 |
For some access points on linked fields no matching terms for an entered key were retrieved, not in the auto-complete list and not in the Find data for the field window. |
CV1-6212 |
Under certain circumstances, thousands separators in numbers in multilingual applications were not displayed when switching the user interface language to a different language. |
CV1-6192 |
There was an error using the scheduler to import records into a multilingual linked field for which the Allow the creation of new linked records option had been disabled. |
CV1-6172 |
The Export to Excel function for the result list always returned numerical values in American format (1,000.00 instead of 1.000,00). |
CV1-6163 |
The display of the Find data for the field window was distorted when the relevant field linked to a numerically indexed field. |
CV1-6086 |
In a table grid, variable domains on linked terms were not respected and disappeared after entering new terms with those domains. |
Last used external thesaurus now remembered by Collections
When one or more external thesauri have been set up for a linked field and in Collections you open the Find data for the field window, then in the Thesaurus drop-down, Collections now automatically selects the thesaurus that you used the last time.
Applicatication fields and URI fields now clickable in Find data for the field window
Clicking a URL in the found terms list in the Find data for the field window, now opens the relevant URL in a new browser window.