Options to test on your layout and I would test in the following order as the lower you go, the greater the possible performance "hit" on your system:
Commit Records--this may need to be automated on another layout if one client is updating data and you want another client's dashboard view to udpate when they update that data.
Refresh Window [Flush Cached join....
Commit Record is the most important thing, but then you need to add Refresh Window that will make FileMaker Pro go and get all information on your layout from scratch again
I've created a button to refresh but is there a way to automate this? Other than using scheduled scripts via the server?
When anything is done on Filemaker GO it seems to update the data straight away without needing to refresh window. But sending data from Computer to Filemaker GO it is not.
Server side is the one option that really can't work here. It has to be client side, if I understand your set up.
But please describe your set up in more detail, it's certainly possible to set up script triggers on the client that is modifying data to help make sure that things update more smoothly.
I think ive got it now.
I've put script trigger on all dashboards using OnLayoutEnter.
And just setup an onTimer script to run a Refresh Window script every 15 seconds. Seems to be working fine, although I think even when you leave the dashboard layout its still refreshing.
You can use install OnTimerScript with no parameters to halt the timer set on a window. If you don't, it will continue to trip as long as the window is open.
Would it be possible to halt on layout change? Or somewhere along the lines of that. So it doesn't keep running when its not needed.