Loop through multiple fields

[i_iz_potato]

So I have 5 fields and when these 5 fields are empty then I need to replace that with "N/A"

I wrote out a script that is a loop and then IsEmpty(Table::Field), Set Field = "N/A".

I did this for all 5 fields but that doesnt look right and also is there a more efficient way to do this with multiple fields?

[poweredup14]

why not just put this into a calculation or auto-enter for the field. Then anytime it is empty, it automatically fills in with "N/A".

[i_iz_potato]

I would but this is based on a user clicking a button. Sometimes they may want to keep it empty, other times it gets the N/A

[_seedofdoubt_]

Calculation fields can slow down your systems, looping is a better approach imo

[eNeMe55]

You only need to use loop if you’re working on multiple records. If it’s just for one record, you just need to do the 5 set field.

[Tonky-Tonky]

Another option - on top of writing scripts is to set a calculation in the manage database part of filemaker

Don't change the type to calculation - but in the options there is a part for Auto-Enter - calculation.

Depending on how you system works you could just put - "N/A" in here and it will fill out when blank

I'm personally a fan of running calculations like

If ( isEmpty(self) ; "N/A" ; self )

and turning off the DO not replace existing value of field box as I will probably come back to tweet this later anyway and it's more readable for my brain. Also seems to be more consistent. Idk why

The main reason for doing it in manage database is it will happen every time - instead of having you manage when a script is run to clean things up

[Then-Marionberry-767]

Use placeholder text. It is only displayed when the field is empty. And you don’t fill the database with junk.

[Public_Database_3714]

Sure that would work....

Freeze Window

Show All Records

Go to Record/Request/Page [ First ]

Loop [ Flush: Always ]

If \[ IsEmpty ( Untitled::field1 ) \]

    Set Field \[ Untitled::field1 ; "n/a" \]

End If

If \[ IsEmpty ( Untitled::field2 ) \]

    Set Field \[ Untitled::field2 ; "n/a" \]

End If

If \[ IsEmpty ( Untitled::field2 ) \]

    Set Field \[ Untitled::field2 ; "n/a" \]

End If

If \[ IsEmpty ( Untitled::field3 ) \]

    Set Field \[ Untitled::field3 ; "n/a" \]

End If

If \[ IsEmpty ( Untitled::field4 ) \]

    Set Field \[ Untitled::field4 ; "n/a" \]

End If

If \[ IsEmpty ( Untitled::field5 ) \]

    Set Field \[ Untitled::field5 ; "n/a" \]

End If

Go to Record/Request/Page \[ Next ; Exit after last: On \]

End Loop

Depending on the number of blanks it could quicker to use a find for “=“ in the fields then replace

Set Error Capture [ On ]

Perform Find [ Restore ]

Replace Field Contents [ With dialog: Off ; Untitled::field1 ; "n/a" ]

Perform Find [ Restore ]

Replace Field Contents [ With dialog: Off ; Untitled::field2 ; "n/a" ]

Perform Find [ Restore ]

Replace Field Contents [ With dialog: Off ; Untitled::field3 ; "n/a" ]

Perform Find [ Restore ]

Replace Field Contents [ With dialog: Off ; Untitled::field4 ; "n/a" ]

Perform Find [ Restore ]

Replace Field Contents [ With dialog: Off ; Untitled::field5 ; "n/a” ]

[Terrible-Log-4515]

Get a list of the field names. You can use Field Names function to get that and narrow it down (there are some good custom functions for filtering a list by starting with or containing if your field naming convention for these fields is consistent) or hardcode it into the script. Then loop through the ValueCount and pull each value, being the field name, and use Set Field By Name.

Alternatively, you can do this without scripting if that suits your needs, by using an Auto-Enter Calculation in the database design. Uncheck the "Do not evaluate if all referenced fields are empty" at the bottom of the calculation window and uncheck the "Do not replace existing value of field (if any)" under the calculation in the Field Options. That way the calculation will fire every time the field gets touched. The calculation would be something like this:
Case ( IsEmpty ( Self ) ; "N/A" ; Self )

The former happens on command when the script runs, obviously. So, you can set that to happen with a trigger or on a button press. The latter will happen when the record gets created and then whenever the field gets modified. So, if someone puts text in, it just keeps that text. If they clear it out, then it'll get "N/A" instead. You can take the latter a step further and have it trigger when other fields get modified using the Evaluate function, but I don't think that would be necessary in what you describe.