Hide a Link to Entry field

[Simon Hall]

I have a table 'Pubvisits' which has a Link to Entry field 'Patricipants (individual)' which uses the entries in a table 'Participants' to select people names, This appears as a horrible entry-per-line list, so I have a Calculated field 'Participants (list)' which shows the entries in a comma delimited string,

I therefore only need the Link to Entry field to display when I am editing the record. How do I hide it when just viewing the record?

[Er Mo]

Hallo

Man kann bei jedem Feld eine Abhängigkeit festlegen . Diese bezieht sich auf andere Felder zb. Kontrollkästchen . Da kann ich die Sichtbarkeit festlegen zb. Kästchen aktief ( true ) = Unsichtbar . Du kannst jetzt selbst das Kontrollkästchen anhaccken oder durch ein Skript umstellen lassen . so werden die Felder die sich auf diesen Kontrollkästchen bezichen Ausgeblendet . Oder du willst es für die ganze Bibliothek machen . Dafür habe ich ein " Einzellauswahlfeld " mit Namen " Menü " das 2 Einträge enthält ( Normal , Einstellung ) . beim Umschalten auf " Einstellungen " werden alle Felder sichtbar . Ein Skript das " Beim Öffnen / Vor der Anzeigen " aktivirt wird stellt das Menü wider auf " Normal " . So muss immer Aktiv die Einstellung ausgewählt werden .

Hello

You can define a dependency for each field. This dependency relates to other fields, for example, checkboxes. Here, I can set the visibility, e.g., checkbox active (true) = invisible. You can then manually check the checkbox or have a script change it. This will hide the fields that depend on this checkbox. Or you can do this for the entire library. For this, I have a "single selection field" named "Menu" that contains two entries (Normal, Setting). When switching to "Settings," all fields become visible. A script that is activated "On Opening / Before Displaying" resets the menu to "Normal." This way, the "Settings" option must always be actively selected.

Ernst

[Simon Hall]

Thanks Ernst

This is exactly what I was stumbling to understand. My immediate problem is solved and I'm going to ponder the wider implications of your response 👍👍

[David Gilmore]

Are you familiar with "Hidden" sections? Essentially you create a sub header (in usually the last area of a page), and set the dependency to hidden, as described by Ernst. Fields occurring after this Hidden section will then be invisible.

So what I do then is create a Check Box (bEditMode is my name). I place that check box after that Hidden subheader, so it is not visible.

I then have two triggers. An "OpenEdit" (Updating an entry) trigger that simply sets that check box, and a "OpenView" (opening An Entry View Card) trigger that simply resets it. The bEditMode checkbox default value is set true, so that this method also will work for when creating an entry.

Then set the dependency of the field or fields you want visible or invisible to the bEditMode check box. And the field(s) you set will only be visible in the mode you want it do be.

And by the way, the bEditMode is also a great field to use as the dependency for that Hidden section field, setting the section invisible with either/both values of bEditMode.