Afternoon all,
So I've been running a monitor on my app. I initially noticed on returning to my home screen (Screen 1) that a gallery on another screen (Screen 2) that is connected direct to the data source (and is filtered, with add column functions and the like) is running while my app is going through the normal home page operations of creating collections, verifying users and so on and so forth.
I remedied this quite easily by making it so that the OnVisible property for Screen 2 creates a collection from the datasource, and pre filters it for the gallery. This stopped these operations from appearing in the monitor when going back to Screen 1.
However, I've also noticed that I have controls on a different screen (Screen 3) that run some calculations based on what a user types into a value box. These calculations use a lookup to a collection I created from a sharepoint list, and which is collected on the loading on Screen 1. The performance hit of these is so miniscule as to be unnoticable, but I am intrigued as to why it's running. And as with the gallery on Screen 2, I was wondering if it is possible to prevent anything taking place on any other screen until that screen is loaded?
I want to add that none of these controls or galleries reference any controls on any other screens. They were either connected to the data sources directly until I used collections, or have always just used a lookup against a collection.
Hope you can help!
