@cbyrne
Ye, I hear what you saying but the component was designed to enable highly accurate filters and we can't lose that. it's needed in the bulk editor and other pages. Maybe adding 2 different filter modes would be helpful to use in general dashboards.

@cbyrne I'd build an overridden mangoUI with development mode enabled, then you can do whatever you want, could likely also do a hack with the userModule, but the overriding would be giving you more freedom

Fox

@cbyrne
I second all your comments about the tags display. It is even worse when you use points with tags in meta data or scripting data source.

@cbyrne I think it is a side affect of why we implemented the 'Sets historical' feature. That is there to allow importing or generating large amounts of historical data which bypass the point-value event system. This prevents an overload of web socket messages and event detectors raising events.

@jared-wiltshire Oh I know... that's a whole other issue. I'm painfully aware how silly this is!

@holzatelier Just a little update on this.
It seems the data points are indeed updated on my system when timestamps are passed along with the JSON data. What I didn't realize is that if the timestamp predates the last entry in the point value history then the browser window needs to be refreshed to show the added historic data value.

So this works for me now besides the missing JSON parsing Error.

Thank you again for your attention.

Perfect, thanks @terrypacker!