Difference between revisions of "Tables For Data Automation"
From dataZoa Wiki
| 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, or HiCharts), use displays ([[ | + | <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 ([[Table_Displays|tables]], [[LatestValues_Displays|latest values]]) |
<br> | <br> | ||
You can create a table specifically for your app which contains all the data needed and then fetch it into your own application. | You can create a table specifically for your app which contains all the data needed and then fetch it into your own application. | ||
Revision as of 14:22, 9 January 2017
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.
- 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
- Requires string (or jQuery) parsing of embed html (some classes to assist)
- Limit of 50 points of historical data per series for tables.
