Dataflows
Your first steps with Dataflows
Different data sources communicate with source systems of all kinds and usually deliver the data in the form of a table. To display this data, you either access it by using controls or first use a script to process it. You can learn how to script data or how to manipulate table data in the corresponding articles. In this article, we will show you how to post-process various data using dataflows, even without deep scripting knowledge. With dataflows you can for example:
- Rename columns and delete unnecessary columns
- Customize data types..
- Add new columns and fill them with content according to a certain logic.
- Join multiple data sources, even from different upstream systems, using joins and combine them into a single table
Dataflows allow you to start from a single table and adjust the dataset step by step until the result is what you need. You can view, change and add to the individual steps for each dataflow in the Peakboard Designer. This way you can easily check if the sequence has the desired effect and if the result appears.
Create a new dataflow
To create a new dataflow, click on […] next to [Data] or right click on it and select [Add dataflow] (1).
Now you have to select your base table (2) and confirm with [OK] (3).
This step is skipped if you click on […] next to the data source you want to use as base table to create the dataflow or right click on it and select [Process data with a dataflow] (4).
Even if several tables are involved in the data transformation at the end, the dataflow always starts with exactly one table. In the text field (5) you assign a unique name for easier identification of the dataflow. Via Add step you can now apply further transformation steps to the table.
In the right area of the dialog all steps already applied are listed. You can change or delete them later. Click on one of the steps and let the dialog area on the left show you the state of the data AFTER this step.
Finally, under [Reload Status] you can set whether the dataflow should be updated at the start of the visualization, at a chosen interval, from a reload flow or together with its source (7).
