Problem with global fields getting wiped out..??

I'm working with a bunch of scripts in FileMaker that make calls to a web host online.  This particular solution is going to be used by different companies, so I'd like to make the domain of the server the scripts are using dynamic so anybody using the solution file can quickly update it.

I created a new table called Global_Config and I added some fields to this table including one called domain.  Then within my scripts I'm pulling the value from this so we can easily change it from the config if/when the domain ever changes.  

It works just fine as long as the value is filled in to my Global_Config fields, however, for some reason all of those fields keep getting wiped out.  I can't figure out why it is, but suddenly the stuff stops working, I run a quick test and I see that it's trying to hit www./something (leaving out the domain.com that would be pulled from the config table.)  

So then I go back and look at my Global_Config layout and the fields are all empty.  

Any information on what could be causing this would be greatly appreciated.  Thanks!
LVL 11
Andrew AngellCo-Owner / DeveloperAsked:
Who is Participating?
 
Will LovingConnect With a Mentor PresidentCommented:
Global fields are not only global to all records in the table but they are temporary in that the values placed in them only exist for the duration of the user's session. The moment you close the file, any values placed in them during your guest session to the server are lost. This allows multiple guest users to place values in those global fields and not affect each other.

In order to have global fields initially populated with a specific value when the file is opened, you need to either 1) populate it on file open via a script, or 2) Stop FileMaker Server, open the file(s) directly in FM Pro, populate the field, close and then Restart the database in FM Server.

If you do the latter method, any values that were placed in a global field when it was in unhosted, single-user mode will be the initial value when a guest opens the file from FM Server. The guest can of course change the value in the field if they have the privileges, but regardless of whether the field is initially populated or blank, any changes made by a guest are lost on opening.

If you are interacting with the file via Custom Web Publishing (CWP) or Instant Web Publishing (IWP) and you want certain values to be in the global fields during those interactions, then you need to use one of the methods above to set them, most likely the second method described.
0
All Courses

From novice to tech pro — start learning today.