Difference between revisions of "Tables For Data Automation"

Revision as of 09:21, 13 December 2016 (view source) SNC (Talk | contribs) ← Older edit		Revision as of 09:23, 13 December 2016 (view source) SNC (Talk | contribs) Newer edit →
Line 12:		Line 12:
	* Use latest values to get current value, prior values and/or (%) changes		* Use latest values to get current value, prior values and/or (%) changes
	<br>		<br>
−	<div class="imgGlyph24 imgRemember"></div>&nbsp;Remember:	+	<div class="imgGlyph24 imgNote"></div>&nbsp;Remember:
	* Requires string (or jQuery) parsing of embed html (some classes to assist)		* Requires string (or jQuery) parsing of embed html (some classes to assist)
	* Limit of 50 points of historical data per series for tables.		* 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:Publishers]][[Category:Developers]]

---

Revision as of 09:23, 13 December 2016

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

You can create a table specifically for your app which contains all the data needed and then fetch it into your own application.

 Some Advantges:

• You can structure the row (series) labels to be easily identifiable
• Label knockouts are available
• Single Fetch for multiple series
• The displays are server cached for speed which is tripped only when underling data actually changes
• Use glname to access multiple datasets via a single table and multiple group lists
• Use latest values to get current value, prior values and/or (%) changes

 Remember:

• Requires string (or jQuery) parsing of embed html (some classes to assist)
• Limit of 50 points of historical data per series for tables.