<?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: Setting ParentId for child rows in Community Chat</title>
    <link>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11665#M1143</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/13246"&gt;@shaked&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;you can implement with the help of SQL Transformations by Workato application by passing CSV File contents or a file from FileStorage and implement the logic in SQL Query, where you can get the required output rows in a single step. Hope you got my point?&lt;/P&gt;</description>
    <pubDate>Thu, 29 Jan 2026 15:32:02 GMT</pubDate>
    <dc:creator>rajeshjanapati</dc:creator>
    <dc:date>2026-01-29T15:32:02Z</dc:date>
    <item>
      <title>Setting ParentId for child rows</title>
      <link>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11663#M1142</link>
      <description>&lt;P&gt;I have a CSV table that contains both parent and child records.&lt;BR /&gt;I need to identify if a row is a child based on a specific value in the Name field.&lt;BR /&gt;The parent is also identified by a specific value in the Name field.&lt;/P&gt;&lt;P&gt;For each child record, I need to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Find the relevant parent record within the same table&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Update the child row’s ParentId field with the value of the corresponding parent&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I am looking for an efficient and clear way to implement this logic in Workato.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jan 2026 14:01:51 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11663#M1142</guid>
      <dc:creator>shaked</dc:creator>
      <dc:date>2026-01-29T14:01:51Z</dc:date>
    </item>
    <item>
      <title>Re: Setting ParentId for child rows</title>
      <link>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11665#M1143</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/13246"&gt;@shaked&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;you can implement with the help of SQL Transformations by Workato application by passing CSV File contents or a file from FileStorage and implement the logic in SQL Query, where you can get the required output rows in a single step. Hope you got my point?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jan 2026 15:32:02 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11665#M1143</guid>
      <dc:creator>rajeshjanapati</dc:creator>
      <dc:date>2026-01-29T15:32:02Z</dc:date>
    </item>
    <item>
      <title>Re: Setting ParentId for child rows</title>
      <link>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11668#M1145</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your response,&lt;BR /&gt;I’m relatively new to Workato and wanted to make sure I’m following best practices.&lt;BR /&gt;In your opinion, would using a &lt;STRONG&gt;Lookup Table&lt;/STRONG&gt; be the right approach here for mapping parent and child accounts, instead of&amp;nbsp; using SQL?&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jan 2026 08:06:53 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11668#M1145</guid>
      <dc:creator>shaked</dc:creator>
      <dc:date>2026-01-30T08:06:53Z</dc:date>
    </item>
    <item>
      <title>Re: Setting ParentId for child rows</title>
      <link>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11681#M1146</link>
      <description>&lt;P&gt;Hi, the solution&amp;nbsp;@&lt;A class="" href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/10258" target="_self"&gt;&lt;SPAN class=""&gt;rajeshjanapati&lt;/SPAN&gt;&lt;/A&gt; 's is ok because:&lt;BR /&gt;Lookup table: Not suitable for large volumes, No complex queries, No relationships&lt;BR /&gt;SQL Collection: You have many records, Advanced SQL queries, You need to make complex queries&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jan 2026 16:16:15 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11681#M1146</guid>
      <dc:creator>francbaviello</dc:creator>
      <dc:date>2026-01-30T16:16:15Z</dc:date>
    </item>
    <item>
      <title>Re: Setting ParentId for child rows</title>
      <link>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11688#M1149</link>
      <description>&lt;P&gt;Thank you for the explanation.&lt;BR /&gt;Since I’m still new to Workato, I wanted to get your guidance.&lt;BR /&gt;In my case, the CSV file is relatively small and contains a limited number of records.&lt;/P&gt;&lt;P&gt;Given this context, would a Lookup Table be a reasonable approach here, or would you still recommend using SQL Collections as a best practice?&lt;/P&gt;&lt;P&gt;I’d appreciate your perspective.&lt;/P&gt;</description>
      <pubDate>Sat, 31 Jan 2026 16:36:11 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11688#M1149</guid>
      <dc:creator>shaked</dc:creator>
      <dc:date>2026-01-31T16:36:11Z</dc:date>
    </item>
    <item>
      <title>Re: Setting ParentId for child rows</title>
      <link>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11690#M1150</link>
      <description>&lt;P&gt;as you mentioned the input is csv file and you can able to retrieve the csv contents and then go with SQL Collections by Workato with create list with csv file, which would be a recommended and best practise.&lt;/P&gt;&lt;P&gt;when you take lookup table, you need to store the csv contents into table and after storing the data into lookup table again you need to retrieve the records, which is un-necessary of adding a step.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Recommended approach&lt;/STRONG&gt;: get csv file contents (already you have) --&amp;gt; create a list with csv file (SQL Collections app) --&amp;gt; Query list (SQL Collections app).&lt;/P&gt;</description>
      <pubDate>Mon, 02 Feb 2026 05:53:13 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11690#M1150</guid>
      <dc:creator>rajeshjanapati</dc:creator>
      <dc:date>2026-02-02T05:53:13Z</dc:date>
    </item>
    <item>
      <title>Re: Setting ParentId for child rows</title>
      <link>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11693#M1153</link>
      <description>&lt;P&gt;I recommend sql collection since we don't know if the table might grow in size in the future.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Feb 2026 09:59:35 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11693#M1153</guid>
      <dc:creator>francbaviello</dc:creator>
      <dc:date>2026-02-02T09:59:35Z</dc:date>
    </item>
    <item>
      <title>Re: Setting ParentId for child rows</title>
      <link>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11695#M1155</link>
      <description>&lt;P&gt;Thank you very much, I use SQL.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Feb 2026 11:18:33 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/community-chat/setting-parentid-for-child-rows/m-p/11695#M1155</guid>
      <dc:creator>shaked</dc:creator>
      <dc:date>2026-02-02T11:18:33Z</dc:date>
    </item>
  </channel>
</rss>

