Release notes: September 25th 2026 grade

Inriver is moving towards more incremental, smaller releases to better and faster accommodate our customers. With smaller, more frequent releases, Inriver will be able to increase the quality and transparency of the releases and identify and mitigate any erroneous behavior that may be caused by the release much faster.

To receive notifications when new release notes are published, please ensure you follow this page by clicking the “follow” button above.

Content Onboarding

Features

Link Entities are now supported

You can now build relationships between entities directly from a source file. Map the identifiers of the two entities you want to connect and choose the link type just as you did before with the relations mapping.

Now, when you select a link type that carries a link entity, the fields on that link entity are now offered in the mapping grid alongside the entity’s own fields, so a single row in your file can both create the relationship and populate the values that describe it.

Mapped fields from the link entity associated with the VehicleItem link type

Link entity grouping is configured per mapping and controls whether several entities referencing the same target share one link entity or each receive their own. Previously these relationships had to be created in a separate manual step inside the PIM per entity or through the API.

Grouping behavior available when importing link entities

Note: Link entity fields appear only once a link type that carries a link entity has been selected. Grouping behavior is set in the mapping configuration panel and applies to the whole mapping.

Who benefits: Data managers and integration specialists maintaining product structure such as bundles, kits and accessories, who previously had to create these relationships outside the import.

Upload a file without the need to use a named mapping

You no longer must select or create a mapping before importing your data. Upload a file and go straight to Map columns. The dialog that used to ask you to describe the nature of the file before mapping is gone; in its place a configuration panel opens inside the mapping view, with import scope and import mode easily available and preselected for you. The suggestion is a starting point rather than a decision, so review it and adjust anything that does not match your file before you continue.

Note – even though Content Onboarding does its best to identify the import scope this is not always possible, so always make sure to validate this when coming into the map step.

Integration configuration now lives above the field mapping instead of the popup dialogue. If you want to see more settings, click on the two arrows to the right.

If you need to change the Import scope or any other settings on the actual run, click on the two arrows on the far right of the configuration panel to get to the settings.

All the mapping configurations easily accessible. 

Automatic identification of a matching mapping no longer runs by default; if you prefer the previous behavior, turn it back on under Settings, General, with the option Auto-match mapping to file.

If you still want the auto-identification of relevant mapping for the file upload, fill in this checkbox 

A named mapping is therefore closer to a template than to a fixed setup. Applying one brings in its configuration and its field mapping, and you remain free to change anything for the run you are about to make — those changes belong to that run and leave the saved mapping as it was unless you deliberately save over it. If you do not name a mapping at all, the run completes without leaving one behind.

In case you want to save or update your mapping for future use then click Save and continue, if not just Continue without saving. 

If you’ve changed the mappings of the run with an applied named mapping, then you get a confirmation mapping when moving to the next step whether you want to update the mapping or continue.

For the technical user: When using the API, the configuration and field mappings of each run are now found under the /api/v1/runimport/{id}/configuration endpoint, while for a named mapping they are still found under /api/v1/sourceimporters and /api/v1/sourceimporters/{id}/mappings.

Note: Existing mappings are unaffected and continue to work exactly as before.

Who benefits: The typical PIM user with column names identical to the PIM model or the user doing occasional import, who previously accumulated saved mappings they never intended to keep.

Improvements

Function preview and validation now work on large files

Previewing a function or formula against a large source file previously timed out, leaving no way to check a transformation rule before running it. Preview now evaluates against the first 20 rows and returns immediately regardless of file size.

Invalid and incomplete functions are also caught earlier. A function that is missing its source field or operation can no longer be saved, so these are reported while you are still in the mapping step rather than surfacing later during validation.

Who benefits: Anyone building transformation rules against production sized files, who previously had to run the import to find out whether a rule was correct.

Fixes

Map data

• The Ignored fields detected dialog appeared when no fields were being ignored. It now appears only when fields are genuinely excluded.
• Changing the import scope did not refresh the list of available target fields, so fields belonging to the previous scope remained selectable. The field list is now rebuilt whenever the import scope changes.
• Uploading a file exported from Enrich did not prompt to transform it first, so it was imported in the wrong shape. The prompt now appears, and system identifier fields are shown correctly alongside it.
• AI mapping was unavailable when a mapping was opened from the Manage Mappings page, even in environments where AI is enabled. The option is now available.

Validate data

• An error raised while updating an entity did not mark the record as failed, so the run reported a success it had not achieved. The failure is now reported.
• Level 2 CVL fields were not populated from the selected level 1 parent value, leaving the dependent list empty. Dependent values are now resolved from the parent selection.
• Applying a fix to all rows with the same error, or applying a remembered fix, revalidated only part of the file. Every affected row is now revalidated.
• A value mapped to an integer field was sent as a decimal and rejected on import. Integer fields are now sent as integers.

Functions

• Preview an incomplete or invalid function returned an error rather than a message. Invalid functions are now reported clearly.
• A failed transformation allowed the run to continue into later phases. A failed transform now stops the run.