Skip to main content
Support

KB Article #178346

Map not parsed correctly after Datamapper upgrade

Problem

-- Sometimes, after a Datamapper upgrade the old maps are not parsed correctly: special characters (from encodings which contain various letters with accents, like the Nordic European ones for example) are no longer visible or are parsed as incorrect symbols.


Example 1:

Original value of an element: <TF_CODE>TF01</TF_CODE>

Parsed value of the element: <TF_CODE></TF_CODE>


Example 2 - fragment of a map code:

Original:

WHEN "Ĺ" { $lowcase = $lowcase & "ĺ"; }
WHEN "Ä" { $lowcase = $lowcase & "ä"; }
WHEN "Ö" { $lowcase = $lowcase & "ö"; }

Parsed:

WHEN "�" { $lowcase = $lowcase & "�"; }
WHEN "�" { $lowcase = $lowcase & "�"; }
WHEN "�" { $lowcase = $lowcase & "�"; }


This issue has been noticed starting with Datamapper 3.1.18 and is visible in all versions up to the newest ones.

Resolution

This has been fixed starting in Datamapper_3.1.18.2 and the fix is ported to all versions newer than this.


To activate it, when starting Datamapper a parameter named "-compat" (the old '-compatRTM307' is deprecated) must be used.

On Windows, this needs to be added in the datamapper.bat