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

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Capture rejected record's column

Hi,

So I know how to capture rejected records of a file, like by using Row>Rejected. This does filter the rejected records,tells us which value is causing the issue and also which line. But it does not tells us which column does that value falls in.

I need to know which column's value has been rejected. Any help is appreciated. Thanks in advance.

Labels (3)
4 Replies
Anonymous
Not applicable
Author

Hi
It does't not contain the information which column has the error, take a look at tschemaCompilanceCheck component, use a custom schema to check the data, the error message thrown by this component point out which column has the error.

Regards
Shong
Anonymous
Not applicable
Author

Thanks for the reply.


Talend makes the faulty value as null.  Is there any way we can change that value, or enter any other value if the value is rejected?



Anonymous
Not applicable
Author

Hi
Read all columns as string type, link the input component to tSchemaComplianceCheck and use a custom schema to check it,

tFileInputDelimited--main--tSchemaComplianceCheck --main-->tlogrow

                                                                                      --reject-->tlogrow

the reject flow contains all the information, the output looks like:
.--+----------+---------+-------------.
| tLogRow_1 |
|=-+----------+---------+------------=|
|id|newColumn1|errorCode|errorMessage |
|=-+----------+---------+------------=|
|a |elise |2 |id:wrong type|
'--+----------+---------+-------------'

 

Regards

Shong

Anonymous
Not applicable
Author

Thanks a lot Shong!


This is working. Actually I yried this component before, but I couldn't use it properly it seems. Wish I would got a solution to this earlier when I posted this, It would have saved a lot of time.


But thanks anyway.