2019-03-27: release Axiell Collections 1.5

Today we release the fifth update of Axiell Collections 1, offering the bug fixes and new functionality described below, but most importantly: version 1.5 is a "performance" release, improving the overall speed of the software, e.g. when scrolling through large record sets or when displaying and navigating large hierarchies.

2019-03-27: relevant bug fixes since 2019-02-26

Short problem description

The record number could not be printed to a Word template.

Error messages genererated by an edit record procedure were not displayed.

Using Bulk create, it was not possible to leave a mandatory but automatic numbering field empty on saving, while this was possible indeed when creating a new record normally. Using Bulk create, such fields are now displayed as read-only and won't frustrate the Bulk create procedure.

Creating a new location name during the Change location task didn't work.

Rerunning a saved search for non-indexed fields gave full collection as result.

New records could be added to data sources that didn't include the Create new records method.

Changes made in Result set edit mode were not saved when edit mode was left.

The OPENFILE function in ADAPL only worked when the Collections interface language was set to English or when a language specific text file was available.

The RECCOPY function in ADAPL copied the term of a linked field instead of the link reference value, even if the linked field in the FACS source and destination databases linked to the same database.

A forced term in an internally linked field was not saved.

In Google Chrome and Microsoft IE11 no decimal separators were shown when a decimal point had been used.

A particular setup of IIIF left the Media Viewer empty.

HTML fields were not displaying correctly when part of a repeating group.

New values in linked fields on the Change locations procedure screen, could be left without having to force the values.

An entered place name in a geolocation field was not copied to the search box in the link window.

The map on the Geographical map tab in the link window for the production.place field didn't react/update when a place name was entered.

When opening a record with multiple occurrences of a geolocation field, while that field was already selected in the Geographical map view, the map zoomed in on a location somewhere in between those places instead of zooming out to show all places.

An updated linked value was not resolved in the linked-from database.

The feedback mechanism was not working when turning a preferred term into a non-preferred term.

The ADAPL system variable &1[3] was 0 for a manually saved record, instead of 1.

Error Value cannot be null. Parameter name: key when saving record after removing occurrence of internally linked field.

An HTML field wasn't displayed correctly in a zoom screen.

The ADAPL system variable &1 always returned the value 1. When in edit mode it should return value 4.

A before-screen adapl wasn't executed if the record was in edit mode.

The record details filter mode Has data didn't work as expected.

Text and field references in the header of a Word template were not printed any more.

Read-only access rights on a linked database were also effectuated on other databases linked to that linked database.

When selecting a term from the Find data for the field window while the Show only <domain> option is deselected, Collections asked whether it should add the linked field domain to it, while the term was already in that domain.

The link window opened from the within the Change locations screen, didn't seem to be data language-aware.

2019-03-08: XSLT+adapl output format support

From version 1.5, Collections also supports output formats which are a combination of an adapl and an XSLT stylesheet. In the list in the Output formats window there's no visual distinction to indicate the technology behind the different output formats. Only when an output format is finished you'll see the difference: XSLT-based output formats usually generate HTML pages which can be saved, viewed or printed from within the browser, while Word template-based output formats generate Word documents.


The different technologies each have their own advantages and disadvantages, so your application manager will now have one more option to consider when new output formats must be made. Creating XSLTs (combined with an adapl or not) is usually a task for a programmer. See the relevant Axiell Designer Help topic for information about how to set up an output format of this type.