<?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: RTDM_Join_Func in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Join-Func/m-p/402798#M641</link>
    <description>&lt;P&gt;I'd say using databases and SQL is one way to do the job, but it's not necessarily.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While it is true that the built-in Data Grid manipulation functions are sometimes limited,&amp;nbsp;on our projects we do sometimes develop DS2 or Groovy "SAS processes" that cover for the missing functionality not yet available with built-in functions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically, the DS2 or Groovy process can take two (or more) data grids as an input and return one as an output.&amp;nbsp; &amp;nbsp;Inside, you do some basic programming with cycles, hash tables e.t.c. to implement whatever processing you need (Left Join for instance).&amp;nbsp; Then on a diagram, you just place the node wherever you need to do the processing and refer to its output instead of a function call.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 10 Oct 2017 15:17:40 GMT</pubDate>
    <dc:creator>Dmitry_Alergant</dc:creator>
    <dc:date>2017-10-10T15:17:40Z</dc:date>
    <item>
      <title>RTDM_Join_Func</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Join-Func/m-p/402166#M634</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. how can i excute a left join between 2 tables (data grids) in the rtdm flow? (there isnt a custom func for it)&lt;/P&gt;&lt;P&gt;2. how can i excute join between 3&amp;nbsp;&lt;SPAN&gt;tables (data grids)? (without using 2 functions - just in one)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks in advance,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;RTDM_User&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 08 Oct 2017 07:56:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Join-Func/m-p/402166#M634</guid>
      <dc:creator>RTDM_User</dc:creator>
      <dc:date>2017-10-08T07:56:16Z</dc:date>
    </item>
    <item>
      <title>Re: RTDM_Join_Func</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Join-Func/m-p/402722#M637</link>
      <description>&lt;P&gt;Hi RTDM_User,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Unfortunately the join options are limited to inner joins when dealing with data grids in the RTDM flow (as you've probably found out by looking at the available data grid functions in the RTDM user guide). Also, as you've noticed, the TABLEINNERJOIN function only works with two data grids, not multiple.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Since you are dealing with data grids, I'd like to ask where these table structures are originating from? If they're originating from a database, you could use a DS2 custom process for manipulating the data before returning a data grid back to the decision flow. In DS2 you can use FedSQL which would accomplish your join requirements (even though joining three tables would still be two separate joins in FedSQL). You can read more about the FedSQL join operations here:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/fedsqlref/67364/HTML/default/viewer.htm#p1q7agzgxs9ik5n1p7k3sdft0u9u.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/fedsqlref/67364/HTML/default/viewer.htm#p1q7agzgxs9ik5n1p7k3sdft0u9u.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2017 12:37:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Join-Func/m-p/402722#M637</guid>
      <dc:creator>needle</dc:creator>
      <dc:date>2017-10-10T12:37:28Z</dc:date>
    </item>
    <item>
      <title>Re: RTDM_Join_Func</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Join-Func/m-p/402798#M641</link>
      <description>&lt;P&gt;I'd say using databases and SQL is one way to do the job, but it's not necessarily.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While it is true that the built-in Data Grid manipulation functions are sometimes limited,&amp;nbsp;on our projects we do sometimes develop DS2 or Groovy "SAS processes" that cover for the missing functionality not yet available with built-in functions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Basically, the DS2 or Groovy process can take two (or more) data grids as an input and return one as an output.&amp;nbsp; &amp;nbsp;Inside, you do some basic programming with cycles, hash tables e.t.c. to implement whatever processing you need (Left Join for instance).&amp;nbsp; Then on a diagram, you just place the node wherever you need to do the processing and refer to its output instead of a function call.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2017 15:17:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/RTDM-Join-Func/m-p/402798#M641</guid>
      <dc:creator>Dmitry_Alergant</dc:creator>
      <dc:date>2017-10-10T15:17:40Z</dc:date>
    </item>
  </channel>
</rss>

