<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Handling data preparation invalid rows in Data Quality</title>
    <link>https://community.qlik.com/t5/Data-Quality/Handling-data-preparation-invalid-rows/m-p/2276822#M3203</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;The short answer is that a proper "rejected" data management in Data Prep/Studio is part of our roadmap. Per the current plan, it's candidate for the 7.3 release.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;This said, today, I suggest you to play around the following scenario: in Data Prep, you can perfectly create a new empty column (such as "reason why?"). When filtering on invalid values in your prep, fill in this column with the corresponding reason using standard mass functions.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Thanks,&lt;/P&gt; 
&lt;P&gt;Patrick&lt;/P&gt;</description>
    <pubDate>Tue, 07 May 2019 09:30:20 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2019-05-07T09:30:20Z</dc:date>
    <item>
      <title>Handling data preparation invalid rows</title>
      <link>https://community.qlik.com/t5/Data-Quality/Handling-data-preparation-invalid-rows/m-p/2276821#M3202</link>
      <description>Hi !&lt;BR /&gt;I created recepie in data preparation which return only the invalid rows.&lt;BR /&gt;The recepie is triggered using tDataprepRun in talend studio on each row in file.&lt;BR /&gt;I would like to know why the rows are invalid (writing the reason to file or log).&lt;BR /&gt;How can i do that base on talend studio and data preparation? (Ignore data stewardship please)</description>
      <pubDate>Sat, 16 Nov 2024 05:54:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Data-Quality/Handling-data-preparation-invalid-rows/m-p/2276821#M3202</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T05:54:55Z</dc:date>
    </item>
    <item>
      <title>Re: Handling data preparation invalid rows</title>
      <link>https://community.qlik.com/t5/Data-Quality/Handling-data-preparation-invalid-rows/m-p/2276822#M3203</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;The short answer is that a proper "rejected" data management in Data Prep/Studio is part of our roadmap. Per the current plan, it's candidate for the 7.3 release.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;This said, today, I suggest you to play around the following scenario: in Data Prep, you can perfectly create a new empty column (such as "reason why?"). When filtering on invalid values in your prep, fill in this column with the corresponding reason using standard mass functions.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Thanks,&lt;/P&gt; 
&lt;P&gt;Patrick&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2019 09:30:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Data-Quality/Handling-data-preparation-invalid-rows/m-p/2276822#M3203</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-07T09:30:20Z</dc:date>
    </item>
  </channel>
</rss>

