https://community.qlik.com/t5/Talend-Studio/tSchemaComplianceCheck-Null-rejection-while-field-is-Nullable/m-p/2304408#M76189 Hi, <BR />I'm puzzled by tSchemaComplianceCheck behaviour toward null values and schema. <BR />It seems that if the schema is coming from a generic schema, nullable fields are not correctly checked. <BR />Here are the tests : <BR />- one generic schema containing 3 Nullable fields <BR />- a job containing a fixedInputFlow and a tSchemaCompliance check. Both components refer to the same Generic Schema <BR />Test 1: <BR />- input contains a Null value <BR />- "check all columns" is used in tSchemaComplianceCheck <BR />=&gt; the input is rejected. <BR />Test 2 <BR />- input contains a Null value <BR />- "check all columns" is unchecked tSchemaComplianceCheck <BR />- the checkbox for the null Check on the 3 columns is activated <BR />=&gt; the input is validated <BR />Test 3 : <BR />- input contains a Null value <BR />- "check all columns" is unchecked tSchemaComplianceCheck <BR />- the checkbox for the null Check on the 3 columns are disabled <BR />=&gt; the input is rejected <BR />I would have expected tests 1 and 2 to validate the input !? <BR />Is it a bug when the "check all columns" is used instead of the column by column check ? Am I missing something ? <BR />Thanks for your help. <BR />Xavier Sat, 16 Nov 2024 13:48:42 GMT Anonymous 2024-11-16T13:48:42Z https://community.qlik.com/t5/Talend-Studio/tSchemaComplianceCheck-Null-rejection-while-field-is-Nullable/m-p/2304408#M76189 Hi, <BR />I'm puzzled by tSchemaComplianceCheck behaviour toward null values and schema. <BR />It seems that if the schema is coming from a generic schema, nullable fields are not correctly checked. <BR />Here are the tests : <BR />- one generic schema containing 3 Nullable fields <BR />- a job containing a fixedInputFlow and a tSchemaCompliance check. Both components refer to the same Generic Schema <BR />Test 1: <BR />- input contains a Null value <BR />- "check all columns" is used in tSchemaComplianceCheck <BR />=&gt; the input is rejected. <BR />Test 2 <BR />- input contains a Null value <BR />- "check all columns" is unchecked tSchemaComplianceCheck <BR />- the checkbox for the null Check on the 3 columns is activated <BR />=&gt; the input is validated <BR />Test 3 : <BR />- input contains a Null value <BR />- "check all columns" is unchecked tSchemaComplianceCheck <BR />- the checkbox for the null Check on the 3 columns are disabled <BR />=&gt; the input is rejected <BR />I would have expected tests 1 and 2 to validate the input !? <BR />Is it a bug when the "check all columns" is used instead of the column by column check ? Am I missing something ? <BR />Thanks for your help. <BR />Xavier Sat, 16 Nov 2024 13:48:42 GMT https://community.qlik.com/t5/Talend-Studio/tSchemaComplianceCheck-Null-rejection-while-field-is-Nullable/m-p/2304408#M76189 Anonymous 2024-11-16T13:48:42Z https://community.qlik.com/t5/Talend-Studio/tSchemaComplianceCheck-Null-rejection-while-field-is-Nullable/m-p/2304409#M76190 Hi, <BR />I think that this behavior might be related to 8212<BR />HTH, Wed, 19 Aug 2009 18:10:34 GMT https://community.qlik.com/t5/Talend-Studio/tSchemaComplianceCheck-Null-rejection-while-field-is-Nullable/m-p/2304409#M76190 Anonymous 2009-08-19T18:10:34Z https://community.qlik.com/t5/Talend-Studio/tSchemaComplianceCheck-Null-rejection-while-field-is-Nullable/m-p/2304410#M76191 Indeed, this is same issue. <BR />I searched the forum for traces of this bug but forgot to check the Bugtracker...<BR />I'll wait for the 3.1.4. version...<BR />Thanks.<BR />Xavier Wed, 19 Aug 2009 18:30:45 GMT https://community.qlik.com/t5/Talend-Studio/tSchemaComplianceCheck-Null-rejection-while-field-is-Nullable/m-p/2304410#M76191 Anonymous 2009-08-19T18:30:45Z