Hi Brad_GMI,

Fox's suggestion of the API is the right one. Without knowing any idiosyncrasies of how you need the data exposed it is difficult to make a definite recommendation other than the API as that is definitely part of its purpose.

Are you restoring a backup from a previous version of Mango into a newer version? That's what it looks like. To do that, you would have to follow the instructions for doing the restore on the command line, so that Mango can follow its normal upgrade procedure during startup. The "eventDetectors" table which is missing was created in Upgrade12, which was released long ago.

You'll want to move your existing mah2.h2.db file before doing the command line restore, for safe keeping.

I have a suspicion the data source page issue would be the one in this thread, with the course of resolution I suspect you will use provided by Jared at the end (unless you are going to upgrade the instance): https://forum.infiniteautomation.com/topic/3551/data-sources-does-not-appear

The problem was more pronounced on the publisher, but I could see how points being updated could cause that. I would really consider moving your installation to MySQL, since you are on 2.8 and MySQL doesn't have the issue.

Hi Brad,

The HTML reports module? I think you are correct, that information is not available. I have added it to the module, though, and it should be available through a PointStatistics object as getPointHierarchyPath() like mapped.p1.getPointHierarchyPath()

Should be released this week.

Also take a look at the "date pickers and presets" example.

It would export without errors, but one of the items in the list of points would be the text: "dataPointId":null

I was just curious if that was related to the issue. Glad you got it working!

Hi Brad,

We have a standard set of instructions here: http://help.infiniteautomation.com/support/solutions/articles/14000022648-how-to-upgrade-mango

@phildunlap Thanks Phil,

I wrote an excel sheet that automated the alias generation.

I'll check out that ftl file and see what I can do.

Hey Brad, from the logs you posted its definitely timing out on the read, i.e. its sending a command and not receiving a response. I know this will happen with AB PLCs when the session is invalid or something like that.

I would try disabling points on your existing datasource until you can get it to work. I suspect its something to do with the payload sizes, i.e. the driver is requesting too much data at once or something. Its odd that it used to work and just stopped though.

Unfortunately the AB datasources are provided by a 3rd party vendor - Deltamation, so we don't have access to the source code to debug or fix the issue. I will forward the issue onto them.

Why yes I do. That would explain everything. One day I will pay attention to all of the available options. One day....

Thanks for the help!

Yep you're quite right, I get the same. Thats odd as the amcharts library automatically loads the rest of the plugins fine and the jszip library is definitely there. I'll check its working for the next dashboards release.

Thanks Guys!

I was able to get things going with your solution Jared.

Below is the basic template of what I am using to get real time values:

<ma-point-hierarchy path="[]" hierarchy="rootFolder"></ma-point-hierarchy> <md-select ng-model="subfolder"> <md-option ng-value="sf1" ng-repeat="sf1 in rootFolder.subfolders">{{sf1.name}}</md-option> </md-select> <md-select ng-model="points"> <md-option ng-value="sf2.points" ng-repeat="sf2 in subfolder.subfolders">{{sf2.name}}</md-option> </md-select> <ma-calc input="points | filter:{name:'Setpoint'} | first" output="setpoint"></ma-calc> <ma-get-point-value point-xid={{setpoint.xid}} point="sp"></ma-get-point-value> <pre ng-if=sp><p>The point name is "{{sp.name}}" and its value is {{sp.renderedValue}}.</p></pre>

This configuration allows me to service many customers using the same style system with one dashboard, which saves a lot of development time.

Thank you for posting your results and investigation!

Nice! Thanks for sharing what resolved it for you!

Implemented the extendApp template and added the themeProvider to my extendApp.js and all is well.

Thanks for the tip! One step closer to finishing up my application.

I'll just chime in here to clear something up, ng-if does create a child scope but this does not mean you cannot access objects on the parent scopes from inside it.

The issue is more with setting values inside a child scope. If you output a variable onto a child scope it wont be visible in the parent scope or any of the sibling scopes. You can solve this by creating an object inside the parent scope then setting properties on the object inside the child scopes. e.g.

This works:

<label><input type="checkbox" ng-model="showInput"> Show Input</label> <div ng-init="parentScopeObj={}"> <div ng-if="showInput"> <!-- we are now inside a child scope --> <input ng-model="parentScopeObj.myName"> </div> <p>My name is {{parentScopeObj.myName}}</p> </div>

This doesn't:

<label><input type="checkbox" ng-model="showInput"> Show Input</label> <div"> <div ng-if="showInput"> <!-- we are now inside a child scope --> <input ng-model="myName"> </div> <p>My name is {{myName}}</p> </div>