"Hiding" a Portal Based on Field Value

[AdamZ]

I've been trying to figure out a solution for this and have gone down this path, although I'm not sure if there's a simpler solution.

Essentially, I'm creating a job application. There are radial selections for "Have you been convicted of a Felony?" and "Are you related to anyone who works for the company?" These are Yes/No fields and are stored in the APPLICATION table.

The problem is that I want to "pop-up" explanation fields only in cases where the answer is yes. For the felony explanation field, that is easy - I have a one line portal that hides itself when the answer is no and it has one field from the APPLICATION table included.

The relationship field is more complicated. Because a candidate could possibly be related to more than one person at the company, I have a separate table called RELATED_EMPLOYEE for normalization with a foreign key related to application_id. I can make the portal disappear using a 2nd relationship between APPLICATION:Related =/= RELATED_EMPLOYEE:RelatedKey. In this case RelatedKey is a calculated field with the value set to "No". However, by using the not-equal relationship, Filemaker greys out the option to create records in that table via the relationship and I cannot enter the relationship details.

When I set the RelatedKey relationship to equal (and change the value to "Yes"), I'm able to create records, but it won't disappear when the trigger field is set to No.

Does any of this make sense?

EDIT: I've uploaded the file as well, but now I'm realizing that nothing is working using "hidden portals" - I can't get the criminal description to hide, and I can't get the previous applications portal to show at all...

IC_Recruiting.zip

Edited July 23, 2010 by Guest

[bcooney]

You could use tab panels (w/o lines so that they are hidden). Clicking the radio button could run a trigger script that switches the panel.

Or, use the hidden portal trick to reveal a button that pops an entry screen for entering relationships if Yes.

[bruceR]

The relation was not set up properly for what you are trying to do. You need to relate in app ID and constant_yes = criminal history.

IC_Recruiting.fp7.zip