Im wondering if im going to have to make this a regular field, then run a script to set a separate global variable to equal that container field.
Why use a global?
1 of 1 people found this helpful
The Global Field (global storage option on a field) is meant to be 'session based' and only "sticks" on files/dbs that are not hosted.
There are several methods to "save-a-value" in a global field once the database is hosted.
1. a normal field with the data and push to global upon startup
2. use an auto-enter data value for the global and when a new record is created the global "updates" with the value
3. and other tricks
We even have "Ideas" here to allow this to be programmatically set:
Its global so the logo prints on different invoices . Im going to just make a reg field for it and then on startup have it set the global fields = to the regular field.
Great, ZM! Please mark the question as "answered" (even if you mark your own decision as 'correct').
Assuming this is your company logo it doesn't need to be global. Simply create a container field on whatever record (company, user, contact whatever) identifies your company and place the field on your invoice layout (which is of course based a related table). As an example I have a layout and table for "production overview". In this table I have a container field with non-global storage that holds a logo associated with each production. A child table records engagements associated with a given production. The logo field is placed on the engagement layout and all instances show the proper logo. I don't see the point in the global.