Release notes

Filter and view release notes relevant to you. Visit our ideas portal for feature requests, a private forum designed as an interactive space where our customers can post ideas, vote on other ideas and receive feedback from the INX Software product team.

Email updates

Subscribe
13 Aug 2025

Improved error logging for duplicate employees in Ad Hoc Leave integration and added support for more custom field types

V 2025.1

Available from 18 August 2025

 

Improvements

 

Improved error logging for duplicate employees in Ad Hoc Leave integration

Improved error logging when assigning leave to an employee with a duplicate EmployeeID in Quartex Core. Record log will now contain validation message of “EmployeeID [Duplicated-ID] is duplicated in database”.

Added support for more custom field types

The newly added support types are:

  • Selects (All custom fields)
  • Date (All custom fields)
  • Time (All custom fields)
  • Multi-selects (Event custom fields)
  • Person (Event Custom Fields)
  • Workgroups (Event Custom Fields)

Add event customfield metadata

Add support for custom fields in the “Event Base” integration

Case-insensitive lookups for CPKs

Add case-insensitive lookups for primary keys

 

Fixes

 

Fix for silent failures when no valid records in payload

Fix error notifications when no payload contains no valid records. This could previously fail silently.

Fixed error on fields which are both foreign and primary keys

Fixed an issue where integrations were failing when referencing the foreign keys of primary key fields.

Fixed a crash for exports on certain integration types

Fixed crashes for exports on the following integrations: Event Participants, Exposure Hours, Person Worksite, Roster Cycles, Roster Actual Work Days, Roster Definitions, Rosters Person Planned, Person Competencies, Person Compliances, Person Procedures.

Validation of mandatory fields with defaults

If a field is mandatory and has a default, the default is used unless a ‘null’ value is provided. In that case, the ‘null’ value will be validated, and should fail the validation process as the field is mandatory. Previously, this validation step didn’t validate ‘null’ values correctly, resulting in no error messages if a record tries to set a mandatory field with a default to ‘null’. This validation was fixed so both the record in question is processed correctly, and all error logs are output as normal.

Back to list
Contact us