I have a multikey relationship that links one person to another with a join table. The join table has IDs from two records in the people table. This allows me to link everything just fine, but the only way I can currently display only one of the people in the portal is to use conditional formatting to blank out the information for the record being displayed, which means the portal shows both ID records from the join file, but has one conditionally blanked out based off of the current record. And that makes it impossible to correctly sort. Is there a way with a multikey relationship for me to set up a portal that only displays the record that isn't the current record?

In version 11, you can use portal filtering to exclude the current record from the portal. In previous versions, you'd need to calculate a list of linked ID's and remove the "local" ID from the list - then base another relationship on the result.

I'll check tonight, but I'm pretty sure that portal filtering will not work, as I'm not wanting to exclude records, but to parse the opposite record from the join table from the portal. I have a Roster::ID linked to Relationship::ID1 and Relationship::ID2. I then create a multikey with ID1¶ID2 lined to Roster::ID.

I only want to display the opposite entry of this relationship, so if the current record is ID1, I only want to display ID2. If there is a better way to do this, I am open to suggestions.

Thanks,

Robert

Multikeys suck. Avoid them.

Hmm...tricky...You could define a calculation in the People table to filter out the parent key. But since a related record has no way of natively know what parent record is viewing it in a portal, you've got to tell it...with an OnRecordLoad script trigger defining a global variable.

There may be a way of using a self-defining merge variable in a portal, but I haven't tried it.

I don't understand what you are saying here:

I'm not wanting to exclude records, but to parse the opposite record from the join table from the portal. I have a Roster::ID linked to Relationship::ID1 and Relationship::ID2. I then create a multikey with ID1¶ID2 lined to Roster::ID.

Please post a sample file showing your relationships.