Parsed Data does not Match Ruleset Schema
Scenario:
An EXTOL Business Integrator ruleset/business process script that transforms flat file data, into a database table has been working but recently we started to get errors.
After reviewing the set-up it appears that there is an issue with the data itself
Issue:
When examining the .csv delimited we discovered an extra column/field.
EXTOL error message:
Message ID: 278
Primary: Data record #1 contained 208 parsed values. Matching schema record (N/A) contains only 207 values.
Secondary: Parsed values: [SEAN][HOPPE][4321][1000][][][][0][][0][N][][A][SH1001][900001][0][][][][][][0][][][][][1][N][CIA][2][][N][900001][N][2][2][U][S][O][][][0][N][][0][0][SEAN][HOPPE][0][0][][Y][0][0][0][0][][0][0.015][][][0][110078][114232][C][C][C][0][114143][][0][][0][][USD][0][0][0][0][0][0][0][0][0][0][0][0][0][0][WOODS][110022][2][X][][][0][][N][][][][][0][][][0][535][N][Y][Y][Y][N][0][P][1][N][][0][0][N][][][0][0][0][][][][][][][0][0][][][Y][N][][][][][][Y][][1][0][][0][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][0][][][][][][][][][][][][][][0][][0][0][][SRH][SRH][SRH][SRH][][][]
Resolution:
After we removed the extra column/field from the csv delimited data, we were able to translate the data.
By: Sean Hoppe on