Hi Alex,

No, that's isn't possible. You could have a naming schema or XID schema that made filtering the do-not-publish points out of the publisher's "Add points" table, but there is no way to exclude them entirely from that list.

Hi mrlucretius

I got lucky and the first thing I tried was to remove the first div: <div class="ma-designer-root" id="jhodges" style="max-width: 1024px;"> . I actually always remove the default div that the designer creates when I do responsive pages.

Thanks Craig!

Alex,

Are virtual data points different than meta data points?

Yes, briefly,

Virtual points can:

Have simple change types to simulate data easier. Performs a 'change' when refresh point value is called Not be polled so that they're only user updated (data source setting)

While Meta points can

Have a script executed on cron patterns or from point events (updated, changed, logged) Have a script executed when the point's value is refreshed return UNCHANGED; to not update their value

So very different!

Hi Greg, thanks for sharing what resolved it!

Correct! and point well taken - absolutely dumb mistake.

I think simplify is safe to apply to all numeric datapoints? I can't think of a reason why not.

As CraigWeb noted it does not affect logging. It is likely more overhead than the other rollup types, but I wouldn't expect that to be too big a deal. You can use the internal data source to watch if you see significant changes over time.

My advice is to just keep it simple. If you know what you want to achieve, work back from that and break it down.
All else fails, you know we're all here to assist.

Fox

Hi

As Thomas said the issue is probably still caused by the fact that u have absolute positioning. If you use the drag and drop designer, your elements will have an absolute position. This will always cause issues on different size screens. If you want your page to dynamically adjust to the screen size. You will need to use angularjs flex.
Flex uses percentages of the available screen size instead of pixels.

We've talked about and looked into having an easy to use integration with Let's Encrypt, but we haven't done so quite yet. If you do use it though, and you are restarting Mango every time you get a new certificate loaded into a JKS (which is what, every three months?) so that it presents the correct certificate, know that you can tell Mango to reload it's SSL settings, but you have to be using a JKS file in the same file location with the same credentials (but I don't think it matters if you replace the file or update the existing certificates in the existing JKS). After that's in place, you can run this in a script (and just validating the script is sufficient to make it happen)

com.serotonin.provider.Providers.get(com.serotonin.m2m2.IMangoLifecycle.class).reloadSslContext();

You may need to close and open the browser to see the new certificate loaded, or clear your cached site data.

The only real requirement with XID's is that they are unique to any other XID on the system

While true, there may be issues with certain characters in certain situations. It is best to avoid symbols in xids, for that reason: https://github.com/infiniteautomation/ma-core-public/issues/918

It'll probably only work out of the box if the HTTPS connection has a valid certificate. A self-signed certificate would probably get bounced by the HTTP client's default configuration.

Hi Ralf,

Received persistent points, if created automatically, are set to log all data. This is the most typical, and probably correct, choice. However, you could do a different logging type, and I believe it would work, particularly if you did not save real time data (I think with many other logging types, you will not see the history sync work if there is newer data).

So, simple answer: all data.

Alex called us an I assured him there is enough depth in the permissions system to compartmentalize users, which seemed to be the crux of the question when we spoke.

Some more information: https://help.infiniteautomation.com/data-point-and-logging-settings/ but dated so far as not having the ON_CHANGE_INTERVAL setting at that time.