Difference between revisions of "Tables For Data Automation"

Revision as of 09:15, 13 December 2016 (view source) SNC (Talk | contribs) (Created page with " <div class="imgGlyph24 imgIdea"></div> Instead of using the API to loop through and fetch many series for a given app (like mapping), use embeds (tables, latest values) You...")		Revision as of 09:20, 13 December 2016 (view source) SNC (Talk | contribs) Newer edit →
Line 1:		Line 1:
−	<div class="imgGlyph24 imgIdea"></div> Instead of using the API to loop through and fetch many series for a given app (like mapping), use embeds (tables, latest values)	+	<div class="imgGlyph24 imgIdea"></div> Instead of using the API to loop through and fetch many series for a given app (like mapping, or HiCharts), use displays ([[Tables|tables]], [[LatestValues|latest values]])
−	You can create a table specifically for your app which contains all the data needed and then fetch just it.	+	You can create a table specifically for your app which contains all the data needed and then fetch it into your own application.
	<div class="imgGlyph24 imgConcept"></div>Some Advantges:		<div class="imgGlyph24 imgConcept"></div>Some Advantges:
−	* You can structure the row (series) labels to be easily identifiable (knockouts become available)	+	* You can structure the row (series) labels to be easily identifiable
−	* Fetch data for multiple series with a single fetch	+	* Label [[Label_Knockouts|knockouts]] are available
−	* Embeds are server cached for speed which is tripped only when underling data actually changes	+	* 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 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		* Use latest values to get current value, prior values and/or (%) changes
−		+	<br>
	<div class="imgGlyph24 imgDisambiguate"></div> Remember:		<div class="imgGlyph24 imgDisambiguate"></div> 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>
	[[Category:Advanced]][[Category:Displays]][[Category:Publishers]][[Category:Developers]]		[[Category:Advanced]][[Category:Displays]][[Category:Publishers]][[Category:Developers]]

---

Revision as of 09:20, 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.