I have a view embedded 3 times with different params on each instance on my dashboard. It seems when I go to a different page, then back to my problem page, the view does not refresh the bindings. the object on the view that gives me the most issue is an XY chart that I am showing a bar graph of events over the last 24 hrs. I am running my data source from now(120000) then getting my data for the individual hours in a script transform from there. I am thinking the problem is that the now(120000) doesn't technically refresh on the view loading. My question I guess, is there a more refined way to accomplish this? or should I just run a refresh binding on view load and call it a day? There are a few other views/components in my project that have similar/weird loading issues, like they just load incorrectly and then after a browser refresh, or time, they fix themselves.
What version of Ignition are you using.
I'm having the same issue in 8.1.20, but there appears to be an update in 8.1.22 that helps resolve this issue. I'll be updating this week.
I have had that issue before as well.
I had read that was an existing issue that IA was aware of, not sure when/if it's been fixed. I am running 8.1.23 but I have already stopped using embedded views in the places where I had noticed the issue so i don't know if the issue is fixed or not.
8.1.22
I have a ticket I am hopefully get this resolved with today and will update this topic with.
Any chance you could show this binding and transform you have configured? Your description isn't very clear into how everything is set up.
My ticket is being reviewed. there seems to be an issue with having the now(x) inside a view that is embedded 3 levels deep. re-addressed the original base binding to a param and then tied that param to "now(120000)" on the view that is using this embedded and it works like that.
I suspect it probably has to do with the page lifecycle and perhaps how you're performing navigation, but I'd need pretty in-depth knowledge of your project to be sure.
Theoretically, if you perform navigation via HTTP (links, or direct manipulation of the URL bar content), you're navigating to a new Page, and the old page is "orphaned" as the connection is lost when the browser tab connects to the new Page. If you then navigate back to the orphaned Page before it has been removed from the Session the Views don't start up again because they already loaded for the Page; the binding already thinks it refreshed in the last couple of minutes, and so won't refresh until two minutes after the orphaned Page was originally opened.
using the menu tree object. it doesn't seem to be navigation related unfortunately. I will update once I hear back from Ignition Inductive Automation if they figured out why it doesn't work as expected. Found the work around of assigning it to the param for now at least.
But how are you supplying your target values inside the Menu Tree? If you're supplying a full URL you would be performing an HTTP request. If your target values have a leading slash (and are therefore mounted paths, eg: /somePath/myPage) then you're using Perspective's internal navigation. The HTTP request navigation route would explain what you're seeing.
/TPF/Milling/SupervisoryDashboard, using the page URL.