Customer Portal

Looking for a better error output

Comments 4

  • Avatar
    the_goat
    0
    Comment actions Permalink
    If I understand correctly, you do not have this output from FlatFileReader/UniversalDataReader? Or you're talking about very different component here?

    FFR_error.PNG
  • Avatar
    jcatoe
    0
    Comment actions Permalink
    Interesting, is that only for FlatFile and Universal because most of my graphs use the SpreadsheetDataReader and it gives me:

    <Record fieldDelimiter="|" name="SpreadsheetDataReader_Error" recordDelimiter="\n" type="delimited">
    <Field name="recordID" trim="true" type="integer"/>
    <Field name="file" type="string"/>
    <Field name="sheet" type="string"/>
    <Field name="fieldIndex" trim="true" type="integer"/>
    <Field name="fieldName" type="string"/>
    <Field name="cellCoords" type="string"/>
    <Field name="cellValue" type="string"/>
    <Field name="cellType" type="string"/>
    <Field name="cellFormat" type="string"/>
    <Field name="message" type="string"/>
    </Record>


    The cell value exists but it's not always easy to tell what actually happened with that row.
  • Avatar
    the_goat
    0
    Comment actions Permalink
    Oh, thought we're talking about CSV files here. Let me think about a solution here, should be workaroundable. What kinds of errors those usually are? Conversion ones?
  • Avatar
    Vladimir Barton
    0
    Comment actions Permalink
    Hello Jcatoe,
    there are a couple of different options that you can choose in this situation. However, they can be summed up in these 2 general approaches basically:
    • Converting the XLS(X) file into a CSV file and then reading the CSV file using the FlatFileReader component (as demonstrated by the_goat in the screenshot).

    • Reading the XLS(X) file as if all the fields were string-type fields and then using the CloverETL functions and features to validate and convert those fields into their respective types if possible.

    Please note that these options would make sense only if the errors you are dealing with are purely conversional (for example, when trying to read a string-type field as integer). At this point, I believe it would be most beneficial for an efficient and effective resolution of this case if you either attached an example graph that tries to read an XLS(X) file or at least if you listed those various types of errors that you get when reading the XLS(X) file using the SpreadsheetDataReader component.
    Kind regards,

Please sign in to leave a comment.