I did come up with an awkward work around--If-Else IF blocks of script that use set field instead of set field by name to modify fields--feels like I'm back designing in FIleMaker 3 when I do it though as I have add another block each time I want to use the same script and button with a different field. It does save having multiple scripts where the only difference is the referenced field, however.
Thank you for the post.
Are the two referenced fields in the same table or related tables?
In my test, Field A contains "Field B" and Field B contains "Test" and I used the following script:
Set Variable: [$X; Value: GetField( Table::Field A )]
Show Custom Dialog [$X; $X]
I get the same result in FileMaker Pro 12.0v4 and FileMaker Go 12.0v7. Running the script from either platform returns "Test" and "Test" for the title and the body of the dialog window; however, if Field A contains the name of a field in an unrelated table, then I return <null> from both FileMaker Pro 12.0v4 and FileMaker Go 12.0v7.
Same table, fully qualified references using Table Occurrence Name::FIeld Name format--script works as expected in Pro but not in GO. I use GetFIeldName to pass this info as a script parameter so that the same script with different button/parameter pairs could modify different fields in different tables.
I'll have to test without the table occurrence name--which is not an issue in Pro to see if that works in GO. And I thought I verified that GetFIeldName is working, but I'll check that also.
TSFalcon and PhilModJunk,
Just wanted to let you know that I ran into this bug yesterday. Perplexing experience to say the least. The code in question worked great on Pro, but didn't on Go, because GetField( ) was returning blank. Even more interesting is that GetField( ) worked fine in a different FileMaker file on that same Go client. In other words, GetField( ) only stopped working in one particular file.
I had a colleague of mine open the file in question while I was having the problem and GetField( ) worked fine for him on his Go client. So the problem appears to be isolated to a particular file on a particular Go client.
The only way to fix the problem was to restart FileMaker Go on my iPhone (aka double tap the home button and swipe FileMaker Go off the screen). Worked fine after that.
If it helps: the file was hosted on FileMaker Server 13.0v3, but that didn't seem to matter. I closed the file via the Admin Console and reopened it. Problem still persisted. I downloaded a local copy of the file via the Admin Console, got the local copy onto my iPhone, opened the local copy, but the problem still persisted. Only restarting FileMaker Go itself fixed the problem.
Other relevant environment info: FileMaker Go 13.0v4 on iOS 7.1.2, FileMaker Pro Advanced 13.0v3 on Mac OS 10.9.4