Difference between revisions of "Tables For Data Automation"

Revision as of 10:34, 3 February 2017 (view source) SNC (Talk | contribs) ← Older edit		Revision as of 11:18, 16 February 2017 (view source) SNC (Talk | contribs) Newer edit →
Line 17:		Line 17:
	* There is a limit of 50 points of historical data per series for tables.		* There is a limit of 50 points of historical data per series for tables.
	<br>		<br>
−	[[Category:Advanced]][[Category:Displays]][[Category:Publishers]][[Category:Developers]]	+	[[Category:Advanced]][[Category:Displays]][[Category:Publishing]][[Category:Developers]]

---

Revision as of 11:18, 16 February 2017

 Instead of using the API to loop through and fetch many series for a given app (like mapping, or HiCharts), you can just use displays (tables, latest values)

Just create a table specifically for your app which contains all the data needed and then use AJAX to fetch it.

 Some Advantges:

• You can mark the row (series) labels to easily identify their data
• Label knockouts are available
• Just one fetch for multiple series
• The displays are server-cached for speed
• A GroupList parameter (glname=... on a table gives access to multiple datasets
• A LatestValues display gives you current values, prior values and/or (%) changes

 Remember:

• Use jQuery (or similar library) to parse the structured classes in the display and get the data values
• There is a limit of 50 points of historical data per series for tables.