<?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: Upsert using Action on data in the tDBOutPut component in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Upsert-using-Action-on-data-in-the-tDBOutPut-component/m-p/2308100#M79474</link>
    <description>&lt;P&gt;If Key attribute is auto generated value then remove that attribute from component and try to run job.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Thu, 03 May 2018 15:53:04 GMT</pubDate>
    <dc:creator>vboppudi</dc:creator>
    <dc:date>2018-05-03T15:53:04Z</dc:date>
    <item>
      <title>Upsert using Action on data in the tDBOutPut component</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Upsert-using-Action-on-data-in-the-tDBOutPut-component/m-p/2308099#M79473</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;I am new to Talend and am trying to achieve the following:&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;I have a table which has a key value (auto generated). It receives a null value (for the auto generated values). My data also contains the ID value which is the business key. I want to create a job which will do an upsert according to the business key (the ID column). The insert part is working (it is not writing any records a record with the ID already exists) however the update part is not working. What do I need to do in order to make it update the values according to a business key?&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2018-05-03 at 5.42.20 PM.png" style="width: 999px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="0683p000009LwsY.png"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/152656i0B9C5B92825F8FA1/image-size/large?v=v2&amp;amp;px=999" role="button" title="0683p000009LwsY.png" alt="0683p000009LwsY.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2018-05-03 at 5.42.39 PM.png" style="width: 999px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="0683p000009LxIQ.png"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/155368i41700A8BE88B0ED6/image-size/large?v=v2&amp;amp;px=999" role="button" title="0683p000009LxIQ.png" alt="0683p000009LxIQ.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2018-05-03 at 5.42.56 PM.png" style="width: 999px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="0683p000009LwfP.png"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/148158iE0E8404AAC701522/image-size/large?v=v2&amp;amp;px=999" role="button" title="0683p000009LwfP.png" alt="0683p000009LwfP.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2018-05-03 at 5.43.14 PM.png" style="width: 999px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="0683p000009LwoR.png"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/157393i519846D30520CC26/image-size/large?v=v2&amp;amp;px=999" role="button" title="0683p000009LwoR.png" alt="0683p000009LwoR.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 15:46:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Upsert-using-Action-on-data-in-the-tDBOutPut-component/m-p/2308099#M79473</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-05-03T15:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: Upsert using Action on data in the tDBOutPut component</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Upsert-using-Action-on-data-in-the-tDBOutPut-component/m-p/2308100#M79474</link>
      <description>&lt;P&gt;If Key attribute is auto generated value then remove that attribute from component and try to run job.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 15:53:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Upsert-using-Action-on-data-in-the-tDBOutPut-component/m-p/2308100#M79474</guid>
      <dc:creator>vboppudi</dc:creator>
      <dc:date>2018-05-03T15:53:04Z</dc:date>
    </item>
    <item>
      <title>Re: Upsert using Action on data in the tDBOutPut component</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Upsert-using-Action-on-data-in-the-tDBOutPut-component/m-p/2308101#M79475</link>
      <description>&lt;P&gt;vboppudi great thanks! worked like magic!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do I need to keep the key definitions on the Business key?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 16:01:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Upsert-using-Action-on-data-in-the-tDBOutPut-component/m-p/2308101#M79475</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-05-03T16:01:15Z</dc:date>
    </item>
    <item>
      <title>Re: Upsert using Action on data in the tDBOutPut component</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Upsert-using-Action-on-data-in-the-tDBOutPut-component/m-p/2308102#M79476</link>
      <description>&lt;P&gt;If you are updating any data in target table yes you need to keep key on business Key.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Thu, 03 May 2018 16:03:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Upsert-using-Action-on-data-in-the-tDBOutPut-component/m-p/2308102#M79476</guid>
      <dc:creator>vboppudi</dc:creator>
      <dc:date>2018-05-03T16:03:09Z</dc:date>
    </item>
  </channel>
</rss>

