<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Best way to structure a UX / logic flow of 2 related tables</title><link>https://community.appian.com/discussions/f/data/38200/best-way-to-structure-a-ux-logic-flow-of-2-related-tables</link><description>Hi! I have 2 related tables that I have access to BUT do not own. Let&amp;#39;s say the 2 tables are Recruiters and Members. Recruiters has an interface showing recruiter records. This is the entry point of the portal. I want to have a column in the Recruiter</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Best way to structure a UX / logic flow of 2 related tables</title><link>https://community.appian.com/thread/143790?ContentTypeID=1</link><pubDate>Thu, 19 Dec 2024 04:54:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:f0c2a8d4-bd9d-45dd-afe0-3126119fe02f</guid><dc:creator>Mathieu Drouin</dc:creator><description>&lt;p&gt;I would suggest the grid with detail pattern.&lt;/p&gt;
&lt;p&gt;&lt;a id="" href="https://docs.appian.com/suite/help/24.3/grid-with-detail-pattern.html"&gt;https://docs.appian.com/suite/help/24.3/grid-with-detail-pattern.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;When you select a recuiter row, simply make another query (using queryRecordType with multiple filters) to the members table and display the results.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>