EDI-TEXT parser didn't include a Unicode characters (such as º ) BC XEngine throws validation error.

EDI-TEXT parser didn't include a Unicode characters (such as º ) BC XEngine throws validation error.

book

Article ID: KB0090321

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect EDI Protocol Powered by Instream -
Not Applicable -

Description

Resolution:
Analysis
========
You are getting this error because the character º is not in the character set for TEXT
    
Resolution
==========

For EDI 2.7.1
--------------
Add the º character to &ltyour BC>/EDI/Validator/Docs/Settings/Production/IDoc_actions.ecs using Spec Builder.


For EDI 2.8.0
--------------
Add the º character to &ltyour BC>/EDI/config/actions-pff.ecs using Spec Builder.

Steps to add a character using SpecBuilder
-----------------------------------------
1. open the file using Spec Builder.
2. Click on first node "SelectedNode"
3. click on child node "PropertyChange"
4. click on "Value" (right side of the window)
5. A popup window will open up; append the new character at the end.
6. Click OK
7. Save the file
8. Exit

Issue/Introduction

EDI-TEXT parser didn't include a Unicode characters (such as º ) BC XEngine throws validation error.