That is a kind sentiment to share, surely!

Anytime

As is in the thread, it's a scripting data source. It's JavaScript that invokes the Java directly. I didn't supply the intended cron pattern, though, probably something like 0 0 0 * * ? for that thread, but maybe someone wants an 8 AM summary instead?

@richard-mortimer said in Pagination for a page:

@craigweb said in Pagination for a page:

Hi Richard

I believe, you do not need your query string function as there is already a component for this. You will need to register you page with the URL of ?page

<ma-state-params on-change="PageStart = $stateParams.page; stateParams = $stateParams" update- params="updateParams"></ma-state-params>

Here is a help document that explains how to use it with a watchlist:
https://help.infiniteautomation.com/linking-to-dynamic-pages

Thanks for that, the PageStart variable is read in as what it should be, but seems to be overwritten when I'm reading in the Settings parameters (no matter where I put it on the page), so even when this is at the bottom of the page:

<ma-state-params on-change="Settings.PageStart = $stateParams.page; stateParams = $stateParams" update-params="updateParams"></ma-state-params>

And this is at the top:

<ma-json-store xid="PageConfigXID" value="Settings"></ma-json-store><!-- page configuration data -->

The value goes from 2 to 0 with this URL: http://mango2:8080/ui/richard-overview-angular?page=2

Any idea how to make the value stick ... ?

Scratch that - I've used two repeats - if the PageStart value doesn't exists - it displays the page as normal, but if it does exist, it does sends it to the second repeat and uses that value for the calculation of where to start the page. Kinda goes against the DRY prinicipal, but works effectively ....

So, in the first instance:

<div ng-if="!PageStart" class="table" ng-repeat="site in sites.sites | limitTo: Settings.PageSize : Settings.PageStart">

And in the second:

<div ng-if="PageStart" class="table" ng-repeat="site in sites.sites | limitTo: Settings.PageSize : (( PageStart - 1 ) * Settings.PageSize)">

Cheers

Richard

@richard-mortimer said in Disable an amChart series upon load:

I was asked to remove one of the series plot from the graph

I was asked to add them back, so glad I asked the question, now it's fixed!!

Cheers

Richard

@mattfox said in maJsonStore (JSON store):

@richard-mortimer I believe when you did | number:1 and | number:0 was more than sufficient. alternatively just use point.value.toFixed(1) and point.value.toFixed() repectively

Thanks - the colon in the | number:1 was interfering with the ternary operator and getting it confused; so, while I could pipe it through, I couldn't modify the final number based on which direction it took - the point.value.toFixed(1) did the correct thing for me ...

Cheers

Richard

@richard-mortimer said in Formatting 'converted' point values:

I'd be curious as to the other reasons, to see whether there would be valid reasons to suggest a change to this?

If you change the suffix as I suggested you will see the change anywhere that the point value is displayed, i.e. on any dashboard (without explicitly formatting it), on any report, on any email, on any built in Mango page such as Watchlists etc.

You also get the benefits that <ma-point-value> provides such as the popup Craig mentioned, the flash on change, the unreliable indicator, the event indicator and the red cross hatching when the data point is disabled etc.

Thanks for the suggestions, I ultimately went a different route with this, and bound a slider to the variable that was previously at the top of the page (which was 30 in the first instance) and allowed the user to select how many days worth of data they wanted to see:

0_1555463825065_014_days.png 0_1555463829221_070_days.png 0_1555463838062_112_days.png 0_1555463848343_500_days.png

The text box is also editable, so they can manually type a number in, if they wish (the '500' example at the end). I did use some of the styles suggested to modify the axes to a different grey to lessen it's impact upon the page, but it also meant that the X-axes date was relevant again, so the requirement to remove it changed (let's just call it 'agile development :). The slider modifies about 10 graphs across the page and works quite fast.

Cheers

Richard

@jared-wiltshire - cheers for that ... I'm still within the great leap of faith from PHP to Angular ...

Richard

Thanks, I've got the following code which displays the current time, and one week ago:

<ma-now update-interval="1 SECONDS" output="time"></ma-now> {{ time }}<br /> {{ time | maMoment:'subtract':7:'days' }}

but I'm not sure how to put it in the statistics part, the following fails:

<ma-point-statistics point-xid="DP_349842" from="time" to="time | maMoment:'subtract':7:'days'" statistics="statsObj"></ma-point-statistics>

as does wrapping it in braces, am I following the right syntax?

[edit]

Looks like I had the right syntax (albeit with the dates the wrong way around):

<ma-point-statistics point-xid="DP_349842" from="time | maMoment:'subtract':7:'days'" to="time" statistics="fuel1"></ma-point-statistics>

The issue was with the value I was selecting:

(Last week: {{ fuel1.minimum.value }}) is correct (Last week: {{ fuel1.average.value }}) is not ....

Cheers

Richard

Fair enough, each to their own. As I said, I've never really noticed it nor I guess had a need for it which is why I've never tried.

@richard-mortimer said in Horizontal split screens for the Dashboard Designer "Edit markup" page:

I gotta say, after an hour of using it, I was impressed ...

Glad to hear you've found something that works for you.

Thanks for having an eye to posterity!