January 5, 201412 yr Hi, this might be something i am not doing right, however.... When i place a new picture (png) into a global container field in my mac FMP13 solution, the field is updated throughout the solution. But, when i then copy the FMP13 file to iPhone to run with FMGO 13, the container field retains the old picture (like it is cached somehow). I have tried flushing cache steps and refreshing object, but this not seem to fix it. The only way to force an update (for the mobile to display properly) is to do a new compressed version or create a new kiosk-version. This is seriously doing my head in Is there some script step or defined way to force the updating of the container fields so when it appears on the mobile device, the field displays the correct image? Thanks in advance. Wayne
January 5, 201412 yr Global fields, like global variables, are session-specific and do not survive closing the file. They are meant for temporary storage. If you need them to survive you need to use regular fields
January 5, 201412 yr Author Global fields, like global variables, are session-specific and do not survive closing the file. They are meant for temporary storage. If you need them to survive you need to use regular fields I didn't plan on that. Makes a whole lot of sense. I will update the "parent" table (1 record) to use standard fields and test it out. I am sure that will solve it. Many thanks !
January 5, 201412 yr Global fields, like global variables, are session-specific and do not survive closing the file. They are meant for temporary storage. If you need them to survive you need to use regular fields On served files that is. In the 'standalone' configuration content of global fields is saved.
Create an account or sign in to comment