<?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: How to compare null values in Data Profiling - Cross Table Analysis in Data Quality</title>
    <link>https://community.qlik.com/t5/Data-Quality/How-to-compare-null-values-in-Data-Profiling-Cross-Table/m-p/2204008#M710</link>
    <description>&lt;P&gt;@Edith Murillo​&amp;nbsp;I have checked with our developers and we confirmed the issue, there is no a workaround now,  however, we have found a way to fix it,  we will add an option to handle the null value on the component.&lt;/P&gt;&lt;P&gt;https://jira.talendforge.org/browse/TDQ-19030&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can watch the jira issue and follow the status.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Shong&lt;/P&gt;</description>
    <pubDate>Mon, 14 Dec 2020 03:49:52 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2020-12-14T03:49:52Z</dc:date>
    <item>
      <title>How to compare null values in Data Profiling - Cross Table Analysis</title>
      <link>https://community.qlik.com/t5/Data-Quality/How-to-compare-null-values-in-Data-Profiling-Cross-Table/m-p/2204007#M709</link>
      <description>&lt;P&gt;Hello all, &lt;/P&gt;&lt;P&gt;I am using the Cross Table Analysis to compare all the columns between two tables. I discovered the #  of rows not matched can have rows that have null values for any of the columns.&amp;nbsp;These rows are in fact the same because the null value exists on both tables for the same column.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a setting I can change to incorporate null values?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's an example, this row was included to the total for # NotMatch when in fact both rows in both tables match because the null value exists in the same column.&amp;nbsp;&lt;/P&gt;&lt;P&gt;TABLE A = 1000404677;Pat;Love;&amp;lt;null&amp;gt;;&lt;/P&gt;&lt;P&gt;TABLE B = 1000404677;Pat;Love;&amp;lt;null&amp;gt;;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 00:58:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Data-Quality/How-to-compare-null-values-in-Data-Profiling-Cross-Table/m-p/2204007#M709</guid>
      <dc:creator>Edith1</dc:creator>
      <dc:date>2024-11-16T00:58:37Z</dc:date>
    </item>
    <item>
      <title>Re: How to compare null values in Data Profiling - Cross Table Analysis</title>
      <link>https://community.qlik.com/t5/Data-Quality/How-to-compare-null-values-in-Data-Profiling-Cross-Table/m-p/2204008#M710</link>
      <description>&lt;P&gt;@Edith Murillo​&amp;nbsp;I have checked with our developers and we confirmed the issue, there is no a workaround now,  however, we have found a way to fix it,  we will add an option to handle the null value on the component.&lt;/P&gt;&lt;P&gt;https://jira.talendforge.org/browse/TDQ-19030&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can watch the jira issue and follow the status.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Shong&lt;/P&gt;</description>
      <pubDate>Mon, 14 Dec 2020 03:49:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Data-Quality/How-to-compare-null-values-in-Data-Profiling-Cross-Table/m-p/2204008#M710</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-12-14T03:49:52Z</dc:date>
    </item>
  </channel>
</rss>

