timeduration Issue When Passed Via URL
When passing a timemode into an Axiom chart URL, the time duration starts from the earliest point of the tag data, rather than from current, when a timeend is not also passed in.
edit: Original post said timeduration, but has been changed to timemode
-
Hi nmaloney ,
I haven't been able to reproduce this on my side. It always loads with the most recent data. Are there any other parameters being passed in? Is this a new chart or a saved chart? Anything you can provide is helpful.
-
Steve Mason I just tried it again with just timeduration and it went to the current time. However, when I add in timemode=Pause, this behavior occurs. I'm curious if you're able to recreate it by adding timemode in as well.
-
nmaloney No difference if I specify a timemode or not. It goes to the recent interval. Are you passing in multiple tags? Are they from a Virtual View or the Local Historian View?
-
Steve Mason I missed this from your first question. I'm seeing this behavior on a saved chart. Also, I believe I mistyped the issue saying that timeduration caused the issue. It's actually timemode causing the issue.
The first picture shows the chart as it opens from the "Open" menu.
If I add "&timemode=Pause", regardless of timeduration, I get the following chart. Notice the April 2024 start date. That is when these tags were first historized.
-
nmaloney , we were able to reproduce this on another machine here so we'll create a bug for it and see if we can figure out what's going on. I was never able to reproduce it on my own machine so I'm not sure what the magic formula is yet.
-
Print this page