From a layout based on Approvers, a portal to Approvals should list all Approvals and only those approvals linked to that Approver. You need only find the correct Approver record for the Approver who has just logged in.
Thanks for the reply. I am finding the correct approver, the issue is that because there are two companies that the approver is assigned to, the approvals for each company appear on a different record. I want them all in one list.
I misread your original post. If your approvers are linked to approvals by ApproverID, you could set up the portal that I describe. Linking by businessID does not appear to be the correct approach here.
But you may need a Join table if you link more than one business to the same approver while also linking more than one approver to the same business. I suspect that this is the ultimate source of the problems you are having--the lack of a proper join table.
You mentioned "applicants that an approver" has been assigned". This implies that somewhere along the line each applicant (regardless of business) has been assigned to one Approver. If that is the case, then to expand your field description a bit:
Then you need a relation from Approvers::ApproverID_pk = Applicants::ApproverID_fk.
Then your portal, assuming that the layout is based in Approvers, would show all related record from Applicants.
Using the text field Approver (as opposed to a serial key), you could have a global text field (in the parent table) that you populate with a list* of Approvers, via a script. You would relate this global field to your child (portal) table. I think that a portal based on this relationship will show a collection of all records related to multiple Approvers.
I hope I understood the question properly.
* - by List, I mean a ¶-separated list of approvers
Yes, I believe this is on the right track. Because the linking is by business ID and there are multiple business ID's, there are multiple records. It is possible that one approver could exist in multiple businesses. I want the approver to go to a screen and see all the applicants that they have to approve without scrolling through records. If I could get all applicants for a single approver, regardless of business, that would be ideal.
How does a join table work?
Your answer does not confirm that a join table is needed.
Yes you have multiple businesses linked to the same approver.
But can there be more than one approver linked to the same business?
You only need a join table if this second item is also true.
Here's how to set up and use a join table, but don't do this unless you truly need to:
Approvers::ApproverID = Approvals::ApproverID
Approvals function as your Join table
You can then put a portal to Approval on an Approver layout to list all Approvals linked to that Approver. Fields from Businesses can be included in the rows of this portal to show the needed info.
Conversely, a portal to Approvals placed on a Businesses layout can be used to list all approvals linked to that business.
that did the trick. I am now able to get the information I need in the portal.