2018-06-22: release Axiell Collections 1.1

Today we release the first update of Axiell Collections 1, offering the new functionality described below.

2018-06-22: relevant bug fixes since release 1.0 (2018-05-18)

Short problem description

After copying a record no new, automatically numbered object number was assigned.

Field groups on screen could appear nested or overlapping.

Starting the Change locations task would generate a "The method or operation is not implemented" error.

In some data sources, a "Language is required" error could prevent the record from being saved.

A drop-down list with flexible sub domains was only available in the primary record, not in linked records opened in a zoom screen.

Using the validation icon in Geographical place fields, would sometimes generate errors.

When for a linked field with a flexible domain the Find data for the field window  was opened without actually selecting a flexible domain value, the window would show no results, instead of all terms, because it used the Show only filter for an empty domain.

Sorting the Result set was not reflected in the Record details view.

After editing a record, the Save button always had to be clicked twice.

Merged-in fields would not be updated after selecting a different linked record.

The main Settings dialog was not okay any more.

The Bulk create records dialog didn't close any more after the second run.

After-field adapls weren't always executed.

The Rights field on the Management details tab for a database for which "specified rights" had been set up, would display a normal entry field instead of a drop-down list with the available access rights.

A category could only be selected each second time you tried it.

Picking a term from the Find data for the field window only worked after clicking twice.

A new object record contained the default value "cm" for the Unit field in an empty field group occurrence.

It wasn't easy to select a date from a date picker any more.

A table grid view in a detail screen box didn't use the screen's field labels.

Starting a new record from a record in edit mode, whlle not saving the current record, displayed the "Save record" text twice and could cause an internal server error.

The "Is between" operator compared both entered search dates to the "Search key (from)" setting for the relevant access point, instead of the start date to that "Search key (from)" and the end date to "Search key (to)".

An HTML field couldn't be exported.

Expanding a branch in the tree in the Hierarchy browser for the first time, scrolled the tree back to the selected record.

Sorting a result set on an enumerative field would sort on the neutral values instead of the translation in the current interface language (or if that was missing, the English translation). With the fix, sorting is applied on all indexed occurrences of the enumeration field but only the first occurrence is displayed in the result set.

Default field values would not appear in a new record.

If a search returned no hits, the Result set view would become inactive.

A pseudonym term was allowed other relations besides the relation to the "main" term.

There was an error when adding an existing currency to an object record.

Adding a new domain to a record returned error "Input string was not in a correct format".

Fields that appear on screens multiple times, were also repeated in output XML for output formats.

The Gallery view showed only the first image added to an object record.

A new, created and edited linked term wasn't saved in the primary record.

Downloaded copies of uploaded multi-media files (TIFF) had a different file size than the original uploaded files.

The Related records view showed incorrect content.

Conditional screens showed when they should have been hidden.

Deletion of a FACS record in a task adapl generated an internal server error 500.

After a search with no matching records, any old search result would still be presented in the Result set.

Axiell Collections didn't allow access to (incorrectly imported) records with a circular reference, making data correction impossible.

Domains, added to a non-preferred record, were not added to the preferred record.

Thesaurus terms with status 'obsolete' were still visible in lists.

In a detail screen table grid, longer column headers were not completely visible.

Selected hierarchies in the link window weren't copied to the search field when you had set the "hierarchical" operator for the access point.

A current location was not linked to an object if the Identification tab was open as well.

Clicking the black arrow in front of terms with (supposedly) narrower terms, on the View hierarchy tab of the Find data for the field window, didn't always show the (correct) narrowers.

Sometimes conditional fields were shown when they should have been hidden.

A "main" term in a pseudonym relation wasn't allowed to have other relations.

Only every second time you tried to copy a value from the Find data for the field window to a linked geo location field was the value actually copied.

After an object record with a new uploaded image was saved, the link to the relevant media record was gone.

Adding more than one image to an object record didn't work.

The Filmstrip of the Media Viewer did not scale all images correctly.

2018-06-22: changes to the Bulk create records functionality

The Add row below, Remove row, Move field up, Move field down, Edit multilingual fields and Close all panels icons have been added to the window context toolbar: they have the same function as they do in the context toolbar of the Records details view.
The Count box has been renamed to Number of records to create box while a Start box has been added to provide an offset for sequential numbers: data that you enter in uniquely indexed fields, like Object number in model applications, will automatically be made unique with a sequential number that starts with the value that you set in the Start box at the top of the window. For example, if you bulk create three records with object number ABCD-001, while you've set Start to 17, then the automatically generated object numbers will be ABCD-00117, ABCD-00118 and ABCD-00119.

2018-06-22: importing records from a csv file

The Import function, which you can start from the main toolbar, allows you to import lines from a csv (comma-separated values) file into an applicable data source of choice, turning each line of data into a new record. (You can save Microsoft Excel spreadsheets to the csv format, as it resembles a spreadsheet format.)


After selecting a target data source the Import dialog opens, to create your field mapping and to select the source csv file to import. The Settings button allows you set the value separator character used in the csv file, a comma or a semi-colon. The csv file has to meet certain requirements though, for the import to go smoothly: please see the full Import topic for more information.


2018-06-15: ad hoc use of custom Word templates

Previously you could only print to predefined output formats as listed in the Output formats dialog, but now you can also print to any custom .docx Word template which is located on your own pc or local network (regardless whether Collections is hosted by Axiell ALM or installed on your local network). No extra Axiell Designer setup required, you only need to create your own Word templates, which is easier than you might think.
The Output formats dialog will show a new Find Word template box with an upload icon right next to it with which you can select the desired custom Word template to print to.


1.Either select the predefined output format you wish to use or click the upload icon next to the Find Word template box to select a custom .docx Word template anywhere on your pc or local network.
When you upload a custom Word template it will currently only be used this once for printing and won't be stored on the Collections server, so next time you wish to print to this output format you'll have to upload it again in the same way.
2.Mark the radio button of your choice to either print All records of the search result, just the records from the search result that you've Marked or only the Current record displayed in the Record editor.
3.Click OK to apply the selected output format: it won't actually be printed just yet. If a custom template has been uploaded, like in the screenshot below, then that output format will be used for printing, while if no custom template has been uploaded then the selected output format in the output formats list will be used.
4.When you print to a custom Word template you get the choice to open the resulting document in Word (after which you can edit and save it under any name) or to save it directly to your Downloads folder (under the same name as the template) without opening it in Word.

2018-05-22: date presentation formats

A date field does not only have a data type, a date format (like ISO date) in which the date is stored in the database, but also a presentation format. Usually the presentation format is identical to the stored format but it can be different too. That way you can enter and present dates in records in your local format, e.g. as a European date, an American date etc., while still saving those dates in the international ISO date standard format. This has now been implemented in Axiell Collections:

When typing a date in a date field in a record, you can use its data type format or its presentation format. The date will always be saved in its data type format and in display mode presented in its presentation format.
When typing a date in a date access point on the Standard search tab, you can use either the data type format or the presentation format of the associated field.
Instead of typing a date, you can always use the calendar (if the field has one) to pick a date.
When entering a search statement on the Advanced search, you must always use the data type format of the date field you are searching.