Debugging your Content-Based Splitting
These lines in the Docsplitter setup file (see page Setup File) display splitting values found in the EDI:
[Debugging]
Content=1
| If set to 1 |
When Docsplitter runs, it displays each value it finds that causes a split, where the value was found, and what output file will get it. See the example below. (One common problem: the value in the ZCBS record has trailing spaces. You must account for these in the splitting map as shown in Creating a Splitting Map) |
| If set to 0 or omitted | This information is not displayed. |
Example
C:\Foresight\Instream\Scripts>"C:\Foresight\Instream\Bin\DocSplitter.exe"
-i"C:\Foresight\InStream\Output\Provider_Results.txt"
-d"C:\Foresight\Instream\DemoData\837I_4010_H_5provider.txt"
-r"C:\Foresight\Instream\Output\Proviider_Report.xml"
-ov"C:\Foresight\Instream\Output\Provider_Report_Valid.txt"
-oi"C:\Foresight\Instream\Output\Provider_Invalid.txt"
-s"C:\Foresight\Instream\DemoData\Content_Based_Split_Auto_Setup.ini "
-fxp -l1
Content Splitting Map Mapping >111111111< to File1 Found Content >111111111< at Level 2000A Start Line 9 Outputting to File1 Found Content >222222222< at Level 2000A Start Line 57 Outputting to File0 Found Content >333333333< at Level 2000A Start Line 105 Outputting to File0 Found Content >444444444< at Level 2000A Start Line 153 Outputting to File0 Found Content >555555555< at Level 2000A Start Line 201 Outputting to File0
Understanding filenames in the Content Section
This Docsplitter output mentions the logical filenames File1 and File0:
Content Splitting Map Mapping >111111111< to File1 Found Content >111111111< at Level … Outputting to File1 Found Content >222222222< at Level … Outputting to File0 Found Content >333333333< at Level … Outputting to File0
The actual filenames depend on the [Content Splitting Map] section of the setup file. For these entries in the setup file
| [Content Splitting Map] | |
| Anderson=111111111 | “file1” |
| BTownDamascus=222222222|444444444 | “file2” |
| Edwards.EDI=555555555 | “file3” |
| “file0” – everything else |
| file0 | The logical name for the file containing the leftover data – the data that was not selected based on the content-based splitting map. It has the filename given in Docsplitter’s –oi and –ov parameters. |
| file1 | The logical name for the file created for data that splits due to the first value in the [Content Splitting Map] section of the setup file. In the example above, it will have Anderson at the end of the filename and contain data split because the value 111111111 was found in the EDI data. |
| file2 | The logical name for the file created for data that splits due to the second value in the [Content Splitting Map] section of the setup file. In the example above, it will have BTownDamascus at the end of the filename and contain data split because the value 222222222 or 444444444 was found in the EDI data. |
You can define any number of files, each corresponding to one line in the [Content Splitting Map] section of the setup file.