<?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 fetch all matching records using data_table_lookup? in Workato Pros Discussion Board</title>
    <link>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10457#M4166</link>
    <description>&lt;P&gt;Yes, to reduce the number of steps and tasks, instead of using &lt;STRONG&gt;Search Records&lt;/STRONG&gt;, I would recommend using &lt;STRONG&gt;SQL Transformations&lt;/STRONG&gt;&amp;nbsp;by Workato application ( with in the query you can pass the conditions as you mentioned in search records action). With this approach, you can query data tables directly within the step. It consumes only &lt;STRONG&gt;one task&lt;/STRONG&gt;, and the output can be stored as a file in &lt;STRONG&gt;FileStorage&lt;/STRONG&gt; — all within a single task execution.&lt;/P&gt;&lt;P&gt;Regarding the data_table_lookup formula — by default, it's designed to return &lt;STRONG&gt;only the first matching record&lt;/STRONG&gt;. I'm not exactly sure why it's built this way, but it might be intended for quick condition checks, similar to how ternary operations work in programming.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Jul 2025 09:44:16 GMT</pubDate>
    <dc:creator>rajeshjanapati</dc:creator>
    <dc:date>2025-07-15T09:44:16Z</dc:date>
    <item>
      <title>How to fetch all matching records using data_table_lookup?</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10454#M4163</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Hello Team,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Has anyone worked with the data_table_lookup formula in Workato?&lt;/P&gt;&lt;P&gt;I'm trying to fetch multiple records from a data table based on a condition, but it seems to only return the first matching record, not all.&lt;/P&gt;&lt;P&gt;Here’s an example of my data table:&lt;/P&gt;&lt;P&gt;Student Name Class Course Joined&lt;/P&gt;&lt;TABLE width="384"&gt;&lt;COLGROUP&gt;&lt;COL width="132" /&gt;&lt;COL width="115" /&gt;&lt;COL width="137" /&gt;&lt;/COLGROUP&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="132" height="20"&gt;StudentName&lt;/TD&gt;&lt;TD width="115"&gt;Class&lt;/TD&gt;&lt;TD width="137"&gt;Course Joined&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;Student1&lt;/TD&gt;&lt;TD&gt;7th&lt;/TD&gt;&lt;TD&gt;Python&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;Student2&lt;/TD&gt;&lt;TD&gt;6th&lt;/TD&gt;&lt;TD&gt;Java&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;Student3&lt;/TD&gt;&lt;TD&gt;7th&lt;/TD&gt;&lt;TD&gt;Java&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;Student4&lt;/TD&gt;&lt;TD&gt;10th&lt;/TD&gt;&lt;TD&gt;JavaScript&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;Student5&lt;/TD&gt;&lt;TD&gt;10th&lt;/TD&gt;&lt;TD&gt;HTML &amp;amp; CSS&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;Student6&lt;/TD&gt;&lt;TD&gt;10th&lt;/TD&gt;&lt;TD&gt;Python&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;Student7&lt;/TD&gt;&lt;TD&gt;8th&lt;/TD&gt;&lt;TD&gt;JavaScript&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;(Assume this table is sorted by Created Time in ascending order.)&lt;/P&gt;&lt;P&gt;When I use the formula below to fetch student names who joined the &lt;STRONG&gt;Python&lt;/STRONG&gt; course, I only get the &lt;STRONG&gt;first matching record&lt;/STRONG&gt;:&lt;/P&gt;&lt;PRE&gt;data_table_lookup("&amp;lt;datatable folder path&amp;gt;", "StudentDetails", CourseJoined: "Python")["StudentName"]&lt;/PRE&gt;&lt;P&gt;This only returns Student1, but I was expecting it to return all matches (like Student6 as well).&lt;/P&gt;&lt;P&gt;I've checked the documentation, but I couldn't find anything helpful for this use case. Would love to know if anyone has come across a workaround or better way to handle this.&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 08:11:36 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10454#M4163</guid>
      <dc:creator>Bhagya_pola</dc:creator>
      <dc:date>2025-07-15T08:11:36Z</dc:date>
    </item>
    <item>
      <title>Re: How to fetch all matching records using data_table_lookup?</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10455#M4164</link>
      <description>&lt;P&gt;Hi &lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/11539"&gt;@Bhagya_pola&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;As per my understanding and experience:&lt;/P&gt;&lt;P&gt;The data_table_lookup formula in Workato is designed to return &lt;STRONG&gt;only the first matching record&lt;/STRONG&gt;, not all matches. This is &lt;STRONG&gt;expected behavior&lt;/STRONG&gt; and is by design — it does &lt;STRONG&gt;not support retrieving multiple matching records&lt;/STRONG&gt; directly.&lt;/P&gt;&lt;P&gt;Same like lookup tables also, with lookup formula, we are able to retrieve only one value, but there we can make use of the "search entries" action to retrieve multiple values.&lt;/P&gt;&lt;P&gt;If your use case requires fetching &lt;STRONG&gt;all records&lt;/STRONG&gt; that match a certain condition (e.g., all students who joined the "Python" course), then you’ll need to use an alternative approach like:&lt;/P&gt;&lt;P&gt;by using SQL Transformations by Workato:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;SELECT&lt;/SPAN&gt; StudentName &lt;SPAN class=""&gt;FROM&lt;/SPAN&gt; StudentDetails &lt;SPAN class=""&gt;WHERE&lt;/SPAN&gt; CourseJoined &lt;SPAN class=""&gt;=&lt;/SPAN&gt; &lt;SPAN class=""&gt;'Python'&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;This will return &lt;STRONG&gt;all matching records&lt;/STRONG&gt;, not just the first one.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 08:54:11 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10455#M4164</guid>
      <dc:creator>rajeshjanapati</dc:creator>
      <dc:date>2025-07-15T08:54:11Z</dc:date>
    </item>
    <item>
      <title>Re: How to fetch all matching records using data_table_lookup?</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10456#M4165</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/10258"&gt;@rajeshjanapati&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Thank you for your input!&lt;/P&gt;&lt;P&gt;My intention behind using the formula was to reduce task consumption and minimize the number of steps in the recipe. Currently, I'm using the &lt;STRONG&gt;Search records&lt;/STRONG&gt; action with filter criteria from the data table, and I was hoping to replace that with a formula-based approach.&lt;/P&gt;&lt;P&gt;Unfortunately, it doesn't seem to achieve the desired result in this case.&lt;BR /&gt;Thanks again for your response!&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 09:06:56 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10456#M4165</guid>
      <dc:creator>Bhagya_pola</dc:creator>
      <dc:date>2025-07-15T09:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to fetch all matching records using data_table_lookup?</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10457#M4166</link>
      <description>&lt;P&gt;Yes, to reduce the number of steps and tasks, instead of using &lt;STRONG&gt;Search Records&lt;/STRONG&gt;, I would recommend using &lt;STRONG&gt;SQL Transformations&lt;/STRONG&gt;&amp;nbsp;by Workato application ( with in the query you can pass the conditions as you mentioned in search records action). With this approach, you can query data tables directly within the step. It consumes only &lt;STRONG&gt;one task&lt;/STRONG&gt;, and the output can be stored as a file in &lt;STRONG&gt;FileStorage&lt;/STRONG&gt; — all within a single task execution.&lt;/P&gt;&lt;P&gt;Regarding the data_table_lookup formula — by default, it's designed to return &lt;STRONG&gt;only the first matching record&lt;/STRONG&gt;. I'm not exactly sure why it's built this way, but it might be intended for quick condition checks, similar to how ternary operations work in programming.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 09:44:16 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10457#M4166</guid>
      <dc:creator>rajeshjanapati</dc:creator>
      <dc:date>2025-07-15T09:44:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to fetch all matching records using data_table_lookup?</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10458#M4167</link>
      <description>&lt;P&gt;Yes, we can go with SQL transformations as well, but I don’t need that for my use case.&lt;/P&gt;&lt;P&gt;I’m using a scheduler (data table polling won’t work for my scenario), and within that, I’m using &lt;STRONG&gt;Search records&lt;/STRONG&gt; as the initial step. So I was looking to set up a &lt;STRONG&gt;trigger condition&lt;/STRONG&gt; using the data_table_lookup formula instead.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 10:49:17 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10458#M4167</guid>
      <dc:creator>Bhagya_pola</dc:creator>
      <dc:date>2025-07-15T10:49:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to fetch all matching records using data_table_lookup?</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10459#M4168</link>
      <description>&lt;P&gt;Yes, got it! While &lt;STRONG&gt;SQL Transformations&lt;/STRONG&gt; are ideal for handling millions of records and applying complex filtering conditions, for your use case, implementing the condition directly in the &lt;STRONG&gt;Scheduler&lt;/STRONG&gt; is a smart idea — it helps you save a step (by skipping the &lt;STRONG&gt;Search Records&lt;/STRONG&gt;) and also reduces task consumption.&lt;/P&gt;&lt;P&gt;However, unfortunately, the data_table_lookup formula &lt;STRONG&gt;does not support retrieving multiple matching records&lt;/STRONG&gt; — it only returns the first match. So in this case, the only viable solution is to proceed with the &lt;STRONG&gt;Search Records&lt;/STRONG&gt; step to fetch all relevant entries.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 11:03:26 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10459#M4168</guid>
      <dc:creator>rajeshjanapati</dc:creator>
      <dc:date>2025-07-15T11:03:26Z</dc:date>
    </item>
    <item>
      <title>Re: How to fetch all matching records using data_table_lookup?</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10519#M4185</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/11539"&gt;@Bhagya_pola&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Just a quick thought:&lt;/STRONG&gt;&lt;BR /&gt;In Workato, using a&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;logger&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or a&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;variable&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;typically counts as one task. Similarly, actions like&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;searching records&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(via data table) or performing&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;SQL transformations&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;also consume one task.&lt;/P&gt;&lt;P&gt;However, there's a key difference:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Logger&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;does not return a usable response for further processing.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Search records&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;SQL transformations&lt;/STRONG&gt;, on the other hand, do provide meaningful output that can be used downstream.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;So, it's important to be smart and choose the option that best fits your use case—especially when task optimization and functionality are both critical.&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards,&lt;BR /&gt;Shivakumara K A&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jul 2025 14:59:38 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10519#M4185</guid>
      <dc:creator>shivakumara</dc:creator>
      <dc:date>2025-07-25T14:59:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to fetch all matching records using data_table_lookup?</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10545#M4194</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/11539"&gt;@Bhagya_pola&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Using datatable_lookup formula we can get only one record because it will used for get &lt;STRONG&gt;one matched record&amp;nbsp;&lt;/STRONG&gt; from table it won't give multiple values but you can apply multiple conditions.&lt;BR /&gt;&lt;BR /&gt;If you want to get the multiple values use search option in data table step and apply filter conditions at there ,it will be best option for your scenario .&lt;/P&gt;&lt;P&gt;Thankyou&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jul 2025 14:13:10 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/how-to-fetch-all-matching-records-using-data-table-lookup/m-p/10545#M4194</guid>
      <dc:creator>Obugari</dc:creator>
      <dc:date>2025-07-30T14:13:10Z</dc:date>
    </item>
  </channel>
</rss>

