Best way to structure a UX / logic flow of 2 related tables

Hi! I have 2 related tables that I have access to BUT do not own. Let'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 interface that holds links to the Members interface. The Members interface must show records in the Members table depending on the value of multiple columns of the recruiter row clicked.

Take note that I do not control any of the 2 tables so I cannot make the "blessed way" of using those columns to build a composite primary key. I need a way to pass those column values to query and filter the records in Members table and display them in Members interface.

How do I structure this UX / logic in "idiomatic" Appian?

  Discussion posts and replies are publicly visible

Parents Reply Children
No Data