Hi,
I was wondering about best practices regarding data feeds for dashboards. How I see it there are different ways you could choose to do this:
- One data feed per source: In this data feed you do basic configuration that is applicable for all widgets on a dashboard. You then have most cnfiguraitons/data calculations "in" the widgets of the dashboard
- One data feed per widget: One specific data feed per intended widget for the dashboard.
- One data feed per source, and then connect these to the different widget-specific data feeds.
Does enyone have a best practice regarding this they could share? What is best from an adaptability point of view as well as for maintenance of the dashboard?
With best regards,
Jessica
#arisaware #aris #aware #datafeed
Harm Verschuren on
Hi Jessica,
My best-practice ;-) is to create a (more or less) generic queries that could be the source of a group of data feeds and widgets. Next I create data feeds that result in providing "one goal", or one specific purpose. And also from a pragmatic point, because a data feed seems to be more flexible to create joins, transformations, etc than the query editor of a widget, i.e. technical restriction.
Finally, I create one or more widgets to visualise that "goal" and do as little as possible modifications in the widget query-editor. Only what's needed to visualise. The reason I mention one or more widgets is because you can visualise the same data using more than one widget. Thus reusing the same data-feed. This ensures widgets visualising the same goal or purpose do not return contradicting results (reproducability).
This workflow or best-practice main goal is to centralise all (most) data-feed handling and prevents scattering data-feed handlings all over the place.
Best regards,
Harm