Welcome to FileMaker.
You're on the right track with a List view (or a portal, really). What you can do is, instead of attempting to build a unique identifier based on what the user sees (i.e., date and location), use the existing unique ID for the ad. Store that in a variable when the user clicks on the item he wants. Return the user back to the appropriate layout, then store the ID value in the FK_ads_ID field.
Voila. Your relationship is set, and you've accomplished your task.
Thank you for the tip! I understand the logic in what your saying, but the technique is beyond me at this phase of my learning. I've been looking into setting variables from user input and haven't found out how to do that yet. I'll do some more digging this evening.
To make sure I understand, I would actually need to set two variables, correct? The current Application Record ID that I am starting in, then switch to new list view layout for Ads, set the variable for the appropriate Ad record (based on user input) then return to the Application Record recorded in the first variable, then assign the second variable to the appropriate field in the Application Record..??
I suspect I am over complicating this. Is there any other simpler way from a child record to view a list of parent records to select from. The reverse is so easy via a portal, seams that FM would have provided a simpler tool to look at a list of items in parent from child.
Typically, no, you wouldn’t necessarily need to set two variables. The normal process would be to spawn a second window (or use a popover) so that your original found set is undisturbed. (Although you usually don’t lose the original found set in the original context anyway.) When you return to the original layout (context) or window, the record you started with should still be the original record (unless something caused it to change).
As to your second question, it largely depends on what you mean by “list of parent records”. If you have a many-to-many relationship (where each child can have more than one parent), then you can just use a portal. If it’s a one-to-many relationship, then each child record only has a single parent, so you can just put the related fields directly on the layout.
So I’m not entirely sure what you’re asking.
Thank you Mike, your feedback nudged me in the right direction. Lots to learn still