Table of Contents

Search

Data Transformation Getting Started Guide

Data Transformation Getting Started Guide

Testing a Parser - Tips

Testing a Parser - Tips

Use the following tips to help you create a Parser more effectively.
Set the Startup Component in the IntelliScript Editor.
You can use the IntelliScript editor to set a Script component as the startup component of the Data Processor transformation. You must define a startup component to run the Script. In the IntelliScript editor, right-click a component that appears at the global level of the Script, and select
Set as Startup Component
.
Check the schema.
The Parser uses an output schema hierarchy and the Parser mapping logic to sort the output. If you see unexpected output, check the hierarchy of the output schema. Check that the element characteristics are defined correctly.
Check the example source.
If the output is missing elements, check the example source file. Verify that the elements and the element characteristics are defined correctly.
Define newline markers.
Avoid
Marker
anchors that search for a newline character followed by a carriage return character
\n\r
. This combination often appears in Windows but not in UNIX. Instead, configure a
Marker
with the built-in
NewlineSearch
component that searches for both the
\n\r
sequence and the
\n
or
\r
character alone.
Use relative file paths.
Use relative file paths instead of absolute file paths. Note that file paths in UNIX are case-sensitive.
Find a root element in a schema.
You can use pattern searching to search for a root element when you add a schema to a Parser. To find a match to any number of characters in a string, enter
*<string>
. To match a single character, enter
?<character>
.