07-17-2019 05:38 AM
Hello,
We have a DIP process that is ordered, with no field delimiters, and a custom separator (pipe symbol). One of the keywords configured in this DIP process is alphanumeric and has a maximum length of 250 characters. However, when the data in the index file for this keyword contains multiple sentences and therefore multiple periods and capitalized letters we are receiving and error: "Wrong number of fields". When the values for this keyword in the index file do not contain multiple sentences we do not receive this error. Here is an example of an item that would cause an error:
field1|This is field 2. With an extra sentence.|field3
Wondering if anyone has any thoughts?
Thanks
Derek
07-17-2019 06:30 AM
Hi All,
I have ran several tests after viewing the index file in Notepad++ and discovering an 'LF' character between the sentences. After removing this character the index files processed successfully. This was hard to spot because opening the index files in plain notepad did not reveal this 'LF' character and there was no apparent new line between the sentences.
I am still curious as to why this 'LF' character affected the process the way that it did because we did not select the 'Newline' separator in the configuration but rather the 'Custom' separator.
Thank you all for your very fast responses.
Derek
07-17-2019 05:58 AM
My suggestion would be to use field delimiters if possible, like double quotes ".
07-17-2019 06:08 AM
Derek,
I created a DIP job in OnBase 18.0.1.55 and copied and pasted your line from your question and was able to import it. Because there's no file path in the line, I configured the document type's default file format to be a Virtual E-Form, so I'm not sure if that changes things but the sentences in the field didn't seem to affect it.
Are you sure that the number of fields matches up, including special fields like the >>File Name, >>Document Type, etc. fields?
07-17-2019 06:16 AM
Hi Sean,
The fields do match up. Here is the field order configuration. Order: 1, Keyword Type: ID - Order: 2, Keyword Type: Reason - Order: 3, Keyword Type: >>Document Type
Here is one that failed today:
7657|Eliminate the spaces in the Invoice. Check the actual invoice to see the correct format.|AP - Reject
Thanks
Derek
07-17-2019 06:20 AM
Hi Sean,
In looking at the index file in notepad++ it appears that there may actually be an 'LF' character in between these sentences. I am thinking that this could maybe affect the import, even though we have a custom separator in the form of the pipe symbol selected and not the newline separator.
07-17-2019 06:59 AM
Derek,
If you open the original file with Notepad++ and from the menu bar select View > Show Symbol > Show All Characters, are there any control characters in the middle of those sentences, like a line feed which Windows' built-in Notepad ignores but DIP likely won't and would cause it to report the wrong number of fields? Or check the end of the line to see if for some reason it's just an LF or just a CR instead of CR+LF.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.