<?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: Problem with table sync in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Problem-with-table-sync/m-p/1791419#M61884</link>
    <description>&lt;P&gt;Why not simply skipping the qualify-stuff and concatenating the current and the history table by unifying the fieldnames?&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;</description>
    <pubDate>Mon, 15 Mar 2021 14:16:58 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2021-03-15T14:16:58Z</dc:date>
    <item>
      <title>Problem with table sync</title>
      <link>https://community.qlik.com/t5/App-Development/Problem-with-table-sync/m-p/1791101#M61849</link>
      <description>&lt;P&gt;I have to similar tables "Current records" and "History records" both have two similar fields&lt;/P&gt;&lt;P&gt;Id_user and Id_course both need to join with a table call course_catalog using the id_course to show the name course and other data.&lt;/P&gt;&lt;P&gt;If I unqualify both fields the process create a Sync table, but i dont wan that.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Dec 2021 21:02:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Problem-with-table-sync/m-p/1791101#M61849</guid>
      <dc:creator>luisguerra</dc:creator>
      <dc:date>2021-12-20T21:02:46Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with table sync</title>
      <link>https://community.qlik.com/t5/App-Development/Problem-with-table-sync/m-p/1791152#M61852</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/7976"&gt;@luisguerra&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is a simple way to handle this scenario, follow these steps:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Rename the column; Id_course to Id_course_h in the History_records table.&lt;/LI&gt;&lt;LI&gt;Add a second column with the Id_course to the Course_catalog table, and renamce it to Id_course_h&lt;/LI&gt;&lt;LI&gt;The table will be associated as expected without any synthetic table.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;hth&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Table-Sync-01.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/51092i31E32C2A418FB005/image-size/large?v=v2&amp;amp;px=999" role="button" title="Table-Sync-01.png" alt="Table-Sync-01.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Mar 2021 04:20:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Problem-with-table-sync/m-p/1791152#M61852</guid>
      <dc:creator>ArnadoSandoval</dc:creator>
      <dc:date>2021-03-13T04:20:01Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with table sync</title>
      <link>https://community.qlik.com/t5/App-Development/Problem-with-table-sync/m-p/1791419#M61884</link>
      <description>&lt;P&gt;Why not simply skipping the qualify-stuff and concatenating the current and the history table by unifying the fieldnames?&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;</description>
      <pubDate>Mon, 15 Mar 2021 14:16:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Problem-with-table-sync/m-p/1791419#M61884</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2021-03-15T14:16:58Z</dc:date>
    </item>
  </channel>
</rss>

