Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
dvorakstephen11
Contributor III
Contributor III

NumberFormatException: For Input String...

I'm returning a NumberFormatException in my tInformixInput component. What's the problem here? I have run this job several times and didn't have this problem when uploading similar data. 
0683p000009MGd5.png

Labels (2)
9 Replies
Anonymous
Not applicable

Hi 
This field contains string values such as "Anthony Jones", but you are using numeric data type to read it. If you uncheck the 'die on error' option on tInformixInput component, these string values will be rejected to the rejected flow. eg:
tInformixInput--main--tMap
                     --reject--tLogRow
Best regards
Shong
dvorakstephen11
Contributor III
Contributor III
Author

My tInformixInput component doesn't have a "die on error" option in any of the component tabs. 
Anonymous
Not applicable

OK, this option is not available on this component yet. Try to read this column with string data type, and then filter the input data and remove the data that is alphabetic, finally, convert the data to numeric data type if needed. eg:
tInformixInput--main--tFilterRow--main--tLogRow
on tFilterRow, check the 'Use advanced mode' box, and write the expression as below:
!StringHanding.IS_ALPHA(input_row.columnName);

Best regards
Shong
dvorakstephen11
Contributor III
Contributor III
Author

The field is intended to contain only string values, so I don't want (and shouldn't have) any numeric data types included. In all of my schemas, the resourcename column is a String data type, but I'm still receiving this NumberFormatException.
Anonymous
Not applicable

Can you upload a screenshot of tInformixInput's schema?
dvorakstephen11
Contributor III
Contributor III
Author

   
0683p000009MGdA.png
dvorakstephen11
Contributor III
Contributor III
Author

I figured it out. For some reason I was leaving out resourceid in my query, even though I'm sure I had it in there before at one point. Thanks for your help.
Anonymous
Not applicable

From your screenshots, I see there are many integer fields, this error must occur on one of these integer fields, can you debug to see which field has the error. 
Anonymous
Not applicable

dvorakstephen11 wrote:
I figured it out. For some reason I was leaving out resourceid in my query, even though I'm sure I had it in there before at one point. Thanks for your help.

Great! and thanks for your feedback!