Oh…but no….that would have required too much thought.

The field is called g_inventoryItem
and has 10 repetitions.

I pass g_inventoryItem as a script parameter and then use:

Set Variable $counter = 1;
Loop
SetFieldByName: Get(ScriptParameter) & “[" & $counter & "]” ; “”
Set Variable $counter = $counter + 1;
Exit Loop If $counter > 10
End Loop

But it says the field is missing

“Customers::” & Get ( ScriptParameter )

Script trigger on exit ‘FullName’ field, passing Get ( ActiveFieldName ) results in: “Customers::FullName”

works beautifully now!! Cheers to short/smart scripts!
1 liner, I love it!!

FileMaker in general is forgiving, and doesn’t care about the extra spaces. It can evaluate FIELD [ 2 ] just as easily as FIELD[2].

‘Set Field By Name’ is less forgiving. The following statement properly executes, inserting the value “Test” into the second repetition of the field.
Set Field By Name ["FIELD[2]“; “Test”]

But this statement results in error 102:
Set Field By Name ["FIELD [ 2 ]“; “Test”]

That should be “GetFieldName”, right?

If I’m right, please feel free to erase this massage after you make the fix. Thanks for SFR!

[code]
Let ([

$field = GetFieldName ( sscode::field ) ; // or a complex calc to determine your target field.
$result = " XYZ" // or complex calc to provide dynamic results depending on target field.

];

$field

)//Let
[/code]

Then you only need to manage your code from one place.

Or you can put two variables in each dialog box $target / $result and set the logic elsewhere in your script using variables.

Alternatively Abstract your logic even further by creating Parameter based Scripts that are reusable. A single Script that handles ALL your Set Field by Names that expects two parameters or global variables, a Target field And Result you pass these to your script it does its job, in case of using global variables have it null the values on completion.

 #( "field1" ; GetFieldName ( TABLE::Field ) ) & #( "field1Value" ; "My Value" ) &
 #( "field2" ; GetFieldName ( TABLE::Field ) ) & #( "field2Value" ; "My Value" ) &etc.

to the script which, for good measure, could have a half dozen or more appropriately numbered Set Field By Name steps in it.

And I'll definitely be making a shorthand GFN() for that function since I can see I'll be using it a lot.

IIf ( not IsEmpty ( GetField(Left(GetFieldName ( Self);Length(GetFieldName ( Self)) -1)) ) ;
                        "<" & RightWords(GetFieldName ( Self);1) & ">"
                        & GetField(Left(GetFieldName ( Self);Length(GetFieldName ( Self)) -1))
                        & "</" & RightWords(GetFieldName ( Self);1) & ">" ; "" )

The result must be text and (unfortunately?) the result must be stored if we want anything to show.
We can now duplicate the FirstName_ field and rename it LastName_ and we don’t have to modify the formula.
As a result, if the FirstName field contains Geoff, the FirstName_ field will show:

<FirstName>Geoff</FirstName>

2 important details :
in the xml tags, we don’t want to display the TableName so it is important to extract only the last word in the GetFieldName. Also note the use of the underscore character as a suffix to the name of the calculation fields. RightWords will ignore this special character so we have to be careful not to use a regular character as this would necessitate an unnecessary longer formula to extract the correct text.
Also, since the calculation fields have stored results, it is better to create all the fieds before populating the database. If you have to add or rename fields afterwards, you can force the updating with a Replace command on the source field (replace the source field by the sourcefield calculation).
Sorry for the long explanation.