#2 Value Translate table files must be encoded in UTF-8

[Christoph Tratter]

If the property bridge service "Value Translation" is
used, the mapping developer must also specify a file
containing the translation table.
This file must be encoded in UTF-8! If it isn't, it can
happen that the property bridge does not produce any
result. Additionally, the error as seen in the
attachment occurs. So, that exception message is a hint
for this problem.

Workaround: Convert the translation table file to UTF-8!

[Christoph Tratter]

Exception messages during reconciliation when the described error occurs