Are my data in the chart always actual
One of the benefits of using Data Jumbo is that your charts will be updated automatically when you update your data in Notion. This guide will explain how this works and what you can expect when you update your data in Notion.
Upon establishing a link between your Notion workspace and Data Jumbo, the application receives the requisite permissions to interact with the selected pages. Any modifications you implement within these pages in Notion prompts an automatic synchronization in Data Jumbo, thereby updating corresponding charts within our platform. When your database contains over 500, Data Jumbo automatically switches your chart to cached mode. You don’t have to do anything.
Cached mode lets you load your charts super fast! It works particularly well when your databases contain lots of rows: over 500. As well, if you share your charts on a website, it’s great to have a reduced loading time.
If your chart is under 500 rows, when you load it in your workspace, it will download the latest data from Notion. It works well when you don’t have a lot of rows, but once you start to have a lot more rows it becomes slow. Really slow. If you have a chart with over 5K rows, it can take up to 5mins. Nobody has time for that.
This is where *cached* charts are useful. Instead, Data Jumbo will load a *copy* of your data which is securely stored on our server. It’s great because it lets a get the latest data in a few seconds instead of minutes. This *copy* is always kept up to date, if you update anything in your Notion database it will update it in your chart, exactly like an *online chart*.
Cached charts always load the latest data from Notion, no worries on that part: if you update rows in Notion, it updates in Data Jumbo. But if you delete rows from your database, Data Jumbo can’t detect it. This is due to the limitations of the Notion API. Thankfully, there are solutions:
You can force Data Jumbo to reload the data of your chart fully. To do that, go to the Data Jumbo chart editor > Source database section > Reload button 🔃. It might take a moment depending on the size of your databases: roughly 1 minute for every 1000 rows.
You can also avoid deleting rows, it’s actually a best practice. The best way to do it is to use a property and a filter. Create a select property in your database or use an existing one to tag which row you want to delete: for example add a status of type “archived”. Then, use a filter in Notion to hide the rows that have the status “archived”. Finally, the most important, add a filter in Data Jumbo, to exclude the rows that have “deleted” as status.
How it Works
Upon establishing a link between your Notion workspace and Data Jumbo, the application receives the requisite permissions to interact with the selected pages. Any modifications you implement within these pages in Notion prompts an automatic synchronization in Data Jumbo, thereby updating corresponding charts within our platform. When your database contains over 500, Data Jumbo automatically switches your chart to cached mode. You don’t have to do anything.
Use cached charts
Cached mode lets you load your charts super fast! It works particularly well when your databases contain lots of rows: over 500. As well, if you share your charts on a website, it’s great to have a reduced loading time.
How does that work?
If your chart is under 500 rows, when you load it in your workspace, it will download the latest data from Notion. It works well when you don’t have a lot of rows, but once you start to have a lot more rows it becomes slow. Really slow. If you have a chart with over 5K rows, it can take up to 5mins. Nobody has time for that.
This is where *cached* charts are useful. Instead, Data Jumbo will load a *copy* of your data which is securely stored on our server. It’s great because it lets a get the latest data in a few seconds instead of minutes. This *copy* is always kept up to date, if you update anything in your Notion database it will update it in your chart, exactly like an *online chart*.
Why you should be aware of that? Because cached charts have some technical limits.
Cached charts always load the latest data from Notion, no worries on that part: if you update rows in Notion, it updates in Data Jumbo. But if you delete rows from your database, Data Jumbo can’t detect it. This is due to the limitations of the Notion API. Thankfully, there are solutions:
You can force Data Jumbo to reload the data of your chart fully. To do that, go to the Data Jumbo chart editor > Source database section > Reload button 🔃. It might take a moment depending on the size of your databases: roughly 1 minute for every 1000 rows.
You can also avoid deleting rows, it’s actually a best practice. The best way to do it is to use a property and a filter. Create a select property in your database or use an existing one to tag which row you want to delete: for example add a status of type “archived”. Then, use a filter in Notion to hide the rows that have the status “archived”. Finally, the most important, add a filter in Data Jumbo, to exclude the rows that have “deleted” as status.
Updated on: 18/06/2023
Thank you!