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 09:00 AM
I should have refreshed the page before replying; we both had the same idea in mind, though! I suspect DIP isn't interpreting the line feed as a field separator but as a record separator, so instead of seeing 1 record with three fields, it's seeing two rows with 2 fields and reporting an error on mismatching number of fields.
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 09:04 AM
Derek,
The LF isn't being treated as a field separator but as a record separator. Instead of that record being treated as a single document with three fields, it's being treated as two documents with two fields which causes DIP to report an issue with the wrong number of fields.
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.