ratherbsailing

Thanks for all this, Comment! I did end up figuring out the SQL within a script, which was quite clean within a popover. Your clarification really helped. However, after that I decided that I'd want to be able to click on that info and go to the related record on another layout... so I ended up making a portal how you described above. It's still relatively clean and gives me the additional formatting options that portals provide. Thanks again for your assistance !

It sounds like using SQL is the way to go, since I'd love to avoid adding more TO's with more TO's tacked on... etc. That being said, it sounds like I need to move on from using a portal to display the info and actually just use a new field? SQL is completely new to me, so I'm just working off what I've researched today. It sounds like what you're describing is adding a new field that would be an auto-enter calculation using an ExecuteSQL() function, and I could display that field (list?) either below the main Portal where I've selected a person, or as a popover? (The popover is a great idea, by the way, thanks for that!) Is that correct? Thanks again, comment!

Basically the setup is as follows: 3 Tables: People, Join-PeopleTask, and Tasks The Join-Table relationships are working well to manage individual people attached to a Task. Adding new Tasks happens in a Form Layout based on the Tasks Table. It shows a detail view of each Task and then the people attached to it (in a portal). We are curious if we can add a way to click on (select) a person from this portal and based on that selection, have another portal below display what other tasks that person is attached to. Logically, if we click off the portal ("no selection"), we'd like that portal to be empty. This will help in quickly determining a persons work load after they are assigned to a new task, without having to go to the Person's Detail page and looking at the portal that displays all the tasks they are associated with from there. I have a global variable $$SelectedPerson that holds the UID of the Person we click on in the first portal, that was a simple script. I think I am stuck on understanding the relationship I need for the 2nd Portal to achieve this, if it's even possible. I've tried using a few of the Self-Self TO's that I already have setup for other stuff, but they haven't worked yet, and I realized I probably just don't have the correct relationship or context setup. Before going relationship TOG crazy I figured I'd ask for advice. Again, I want to be on the Form Layout for the Tasks TO, thumbing through random records there, and when I click on a person displayed in the Join-PeopleTask Portal, to have a 2nd Portal display info not only from the Tasks table (like Id/Task Description/Status/Priority) but also from the People table (Id/FullName/Schedule - yes this stuff would repeat in every portal row). Obviously it cannot only display info from the Task I'm looking at, but from all of the Tasks the Person is attached to. Any suggestions on the cleanest (relationship) way to set this up?

Brilliant. Aha! Multiple Single-Row Portals, essentially turning off all of the Fill & Line attributes, should give me lots of flexibility to mess with the fields I do want individually. That's a step in the right direction, for sure. @comment Thanks for your solution as well! I will try them both out and any other suggestions that come in. Your List() using tab characters might be the easiest to manage everything at once. Understandably so, and thanks for pointing that out. I will say that if you had the full context, it would make more sense as to why they do it that way, even in the long run. But hey, I'm keeping my eye on it.

As a new user, even the basic structure of a solution seems to have hundreds of options for getting started. I'm hoping someone can enlighten me on how to achieve the following: I have a Main Menu layout that works off of a "Main Menu" Table. I have a "Team Contacts" table and layout that shows the 5-8 people that are working on a given project. There are simple fields in this table: Role, FullName, Cell #, Email. Due to the nature of these projects, sometimes additional specialists are required (and are temporarily brought on for different tasks). This is why I set up the "Team Contacts" Layout as a List view: so that we can see all of them at once, and so that the Contacts Layout has the ability to display anywhere from 5 - 8 Records (People) flexibly, depending on the project. Since these are all smaller, team based projects, my company would like to display the "Team Members" of the project on the Main Menu Layout, with their Role and FullName displayed. I have successfully done this using a Portal, but since that rather limits how you format the records (into rows), I want to see if there's a way to be able to have separate fields to drag onto the Menu as if I was doing a Merge Field that applied to only a specific record, say Record 1 of Table: "Team Contacts". That would allow me the freedom I'm looking for in formatting them across the menu, for example along the bottom of the Menu Page, from left to right with Role: Name / Role: Name / Role: Name (appropriately spaced, of course). It's important to note that each FM file that gets started from a template file is its own "Project". There is a "Project Info" Table in the file, but it only contains 1 Record (1 Project) and displays the Name, Description, & Dates of the project. Because of this, one solution I thought of (though it seems rather clumsy) would be to just add a bunch of Fields to the "Project Info" Table, all global fields, and one for each potential person on the team, and all of their info. [Role 1; FullName 1; Cell# 1; Email 1; Role 2; FullName 2; Cell# 2; Email 2; etc]. Then using conditional formatting, I guess it would be easy enough to hide Roles 5-8 and all of the labels for them if they are empty fields. Please tell me I'm thinking about this incorrectly and enlighten me. Thanks in advance!