I’m developing a dashboard widget app and need a way to determine whether my app is rendered in Settings view or just the normal Dashboard view.
I’ve tried using monday.listen("settings"), but this only listens to changes in the Settings inputs. This doesn’t work for my case because I’m already making some input changes in the Settings view, and it doesn’t help me identify the current rendering context.
Does anyone have a solution or workaround to achieve this? It’s quite urgent, and I’d greatly appreciate any guidance or help!
Unfortunately, I encountered an issue. When opening and closing the Settings view, the values for instanceType and appFeature (both name and type) remain the same. The instanceType always shows “dashboard_widget”, and the appFeature name and type also remain unchanged.
I appreciate your guidance, but this approach doesn’t seem to differentiate between the Settings view and the regular Dashboard view in my specific scenario.
That is odd. I tested this on my end and it works well here.
Would you be able to please fill this form adding as much information as possible to it (such as a screen recording showing your script, the steps you take and the result you see) so that our team can take a look into it?
Thank you so much for taking the time to test this and for your suggestion to fill out the form. I really appreciate your help!
After revisiting my app setup, I realized that I don’t actually have a separate Settings feature view. Since my app is a dashboard widget, the Settings are configured directly within the Dashboard feature itself, which is likely why the instanceType and appFeature values remain the same regardless of whether I’m viewing the dashboard or the settings. Given this setup, I think I’ll need to explore a different approach to differentiate between the two (normal dashboard and settings) views. If you have any further ideas or workarounds, I’d love to hear them. Otherwise, I’ll continue troubleshooting on my side.
I am not sure I follow. The settings for a view feature are not a feature on its own. I believe I might be misunderstanding the situation. If you fill the form and send us a few screenshots or a screen recording, our team will be happy to take a look!