That is a wide open question….on any given view, the relation to any underlying data can be very broad, how would you know what you want to refresh and on what data change or what status change of another field or object?  Every view at any given point in time is a snapshot of the data that existed at the moment the record was retrieved.  You would not want the system automatically refreshing every other user view based on every change that was occurring on every field on every table underneath the view in question….that would bring the database to its knees speed wise.  First and foremost you have to train users to understand that a change elsewhere affects their view and if they know a change has occurred, then the manual Refresh is the right answer.  If however you can isolate a specific event on an underlying data field or view that needs to always force an update on an another view, you could create an even to trap that condition and force the refresh - but I would really caution against doing very much of that because that too will end up creating lots of traffic that isn’t absolutely necessary.

Hi @ShawnBerk 

Can an event force a refresh? What is the command for that? Our IT team is trying to program a small event that changes a value in a custom field after a Copy Part (diferred event) and we would like to force a refresh after … but do not know how. 

Thanks in advance for your help!