Table of Contents

What is new in Vendor Catalog 14.0

Vendor import mappings

RegEx replacement support for rule action and import transformation

Business Value

You can now normalize and clean incoming vendor data directly in mapping logic, without creating additional external preprocessing steps. This is useful when supplier files contain variable text formats and you need repeatable cleanup before values are written into Vendor Catalog.

The enhancement extends existing RegEx behavior so you can keep current extraction-based mappings unchanged while also enabling advanced replacement scenarios for new mappings. This reduces maintenance effort and improves mapping reliability across suppliers that use different naming, formatting, or composite value patterns.

Where to start

  1. Select Search (Alt+Q), enter Import Data Mappings, and open the page.
  2. Open an existing mapping or create a new one, then open Import Mapping Card.
  3. If you work with Excel mapping, use Sheets From Excel and then Mapping From Excel to generate mapping lines.
  4. Open the relevant mapping line and configure transformation settings in Transformation Expression and related transformation parameters.
  5. In RegEx transformation parameters, set expression, match no., optional replacement, and optional use whole input text according to the target normalization outcome.
  6. Run import processing and verify that transformed values are written in the expected structure before activation.

Technical Changes

The update extends codeunit PIMX Import Transf. Regex (object 4006623) to support replacement templates in addition to existing match extraction. New parameters were introduced for replacement and use whole input text, while keeping default parameter values compatible with previous behavior. The implementation now supports group-reference templates (for example, \1) and resolves replacement for a selected match or for the whole input text.

The implementation also adds parsing and validation paths for replacement behavior, including template tokenization, group-value substitution, and safe fallback when input does not match expected patterns. This keeps transformation evaluation deterministic in import execution while enabling broader data cleanup scenarios without changing the external import flow objects.