File Node is moving the file from read location to Error location

Legacy Contributor

Hi,

I am new to ION and trying to write a document flow to read the CSV file and map it to the SourceSystemJournalEntry so that I can load the GL transactions in GLTransactionInterface business class. For this I have file node, mapping node and application node. Now when I place a file in the read directory for document flow to process it, it getting moved to error location and i didn't understand why its happening, its not showing me any error in ION. Can someone please help me to understand why my file is getting moved to error location from read location ?

Also to achieve what I have describe above what verb I should be using in File Node and Application Node ? 

 

Thanks 

Legacy Contributor

Hey there,

You can always check ION's OneView application and filter for activities that took place during the last hour to have a quick look into whether any issues were reported. Additionally, ION has logging features for on-prem installations where you can pull down log content to search for deeper issues that may not otherwise be reported in OneView.

But I suspect the issue stems from how you're handling the CSV file to begin with. I would recommend double-checking that you've correctly defined the fields to match your CSV file. Here are some things you can begin investigating:

• Double-check that you've correctly identified the right number of fields in your File Template definition
• Ensure that you've correctly defined the handling properties of how ION should parse through your CSV file. Could the new line delimiter be incorrect?
• Have you or do you need to define field enclosing characters? If your data has a comma in one of your values, ION could be identifying this as a delimiter and thinking it's on to the next column.
• Check that the data type (e.g. string, int, decimal, etc.) correctly matches the content of the CSV's columns. When you uploaded a sample file to generate your metadata in File Templates, ION infers the data type based on the content it detects.

In other words, let's say your CSV file has a column named "ID" that can contain any kind of value such as:

• 1
• 2
• 3
• A1
• A2
• A3

Well, let's pretend that the sample file you uploaded as a precursor to generating your metadata used the value "1" in the ID column. Unless you have multiple lines in your sample CSV that have other values like "A1", ION will infer that your column's data type is a int. That'll cause quite a few issues when you go to upload your CSV file to a file directory since ION is expecting to see an integer-based value but should really be defined as a string.

Hope this helps with a place to start investigating!