2 - Major changes in the build experience you should know before starting the migration tasks
Previous1 - General tasks to have your apps running on Toucan V3.0Next3 - Specific tasks depending on your use cases and app design
Last updated
Last updated
The objective of this page is to highlight the new way datasets & filters work in V3 and how it will impact your experience
On the v3, all datasets including stories-tiles-filters datasets are available in the datahub. Once we will have migrated one of your app in v3, you will be able to find datasets for the stories-tiles-filters/requesters under the tag “v3-migration”:
Filters on the v3 are all reunited in one place and can be reused across your app. After migration, you will notice some of your filters might be duplicated:
This is because on v2, for each new story, you create dedicated filters and after migration they are all in the same place:
Requesters with duplicated IDs will be migrated into a single V3 filter; we will use the first requester sharing an ID as the one to keep.
While all new filters will be named in V3, migrated filters won’t be named.
Display change in filters: now in v3, story filters are all displayed in the dashboard header, whereas in v2 they would stay inside the story.
Smart Editor is our latest feature to create tiles, stories (including charts & KPIs) and filters in just a few clicks.
You are wondering what are the most common type of Shark attacks, and you are getting to this result through the creation of leaderboard tile
In order to get there you had to go to specific data preparation step in order to create the perfect dataset required for a leaderboard tile
In V3 you simply select the input dataset (corresponding to the first step of the screen above) and then you select the column to aggregate and the operation type and the rest is all done.
https://docs-v3.toucantoco.com/visualizations-and-layouts/apps/stories/creating-a-story
We will migrate each dataset created by builders to create a chart in V2 into a dataset global to the app (see “Reusable Datasets”). In order not to add any extra operation through the smart editor on “already prepared dataset” we created a “No aggregation” operator. See the diagram below
