# Refresh Dashboard After User Interaction **URL:** \ **Category:** Help\ **Tags:** dashboard, workflow\ **Created:** [May 20, 2019, 3:31pm UTC](https://forums.losant.com/t/refresh-dashboard-after-user-interaction/1806 "2019-05-20T15:31:10Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![anaptfox](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/anaptfox/32/873_2.png) [@anaptfox](https://forums.losant.com/u/anaptfox)\ **Post date:** [May 20, 2019, 3:48pm UTC](https://forums.losant.com/t/refresh-dashboard-after-user-interaction/1806/2 "2019-05-20T15:48:05Z")
@Leo_Bach1 Unfortunately, the problem here is that [Endpoint Reply Node](https://docs.losant.com/workflows/outputs/endpoint-reply/) can not respond to a Virtual Button (because it’s not an Endpoint). This best thing here is to have this form be an HTML form. Then, you can properly redirect the user after form submission. It would be very similar to the approach we took in this post: > [@Input Control Block Dropdown Option Flexibility](https://forums.losant.com/t/input-control-block-dropdown-option-flexibility/1778/5): > > Hi @Leo_Bach1 While I think that making the dropdown selectors a little smarter is a good idea, what you’re trying to accomplish is better done in an [Experience Page](https://docs.losant.com/experiences/views/) rather than a Dashboard Page. Dashboard Pages are not meant for user input from within an Experience – really they should not be interacting with your Experience’s application logic (“Assign Sensors to Machine” for example). From within an Experience, Dashboard Pages should be focused on displaying device data or interacting with … --- _[View the full topic](https://forums.losant.com/t/refresh-dashboard-after-user-interaction/1806)._