Best practice data feed for dashboards

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

Hi Harm,

Yes, that is exactly how I do it. 

It's a bit difficult to see which query relates to which data feed. For that purpose, I also tried to implement a naming convention for the queries that allows me to identify that relationship easily.

Best,

Veronika