Handling of relation columns
In the latest update to Data Jumbo, we've introduced a unique behavior for handling relation columns. By default, these columns will display Notion IDs rather than their actual contents. If you wish to include the resolved contents of relation columns in your charts, you will need to follow specific steps. This process ensures that your charts accurately reflect the data you intend to visualize.
Go to editor mode
Go to tab "Source"
Hover over relation column
Toggle ON to fetch actual relation values
Relation values are going to fetch and this can take while depend on database row size
So that you can immediately recognise whether a relation column contains notion IDs or actual value. We have introduced to icons:
Relation column has Notion IDs
Relation column has actual relation content
Unfortunately, Notion does not immediately return the resolved relation names via the API. We have to read the data from the relation databases in a second step. As this process requires a long loading time or update time, we have decided in favour of this method. In some cases it can improve the loading speed by up to 80%. It is therefore always important to ensure that only the relation columns that are actually used are activated or deactivated.
No, it is a global data jumbo setting, which is fixed to the explicit Notion database.
This means that if I have activated the column relation "Sales" in Chart 1, the relation column "Sales" will also be activated when I open Chart 2. No matter on which chart this is activated or deactivated, it is the same everywhere.
Of course, we don't want to stop here. We want to automate this behaviour in the future. This means that as soon as you use a relation column in your chart, we will automatically recognise this and load the data accordingly, as well as when the column is no longer used. We will inform you as soon as we have more information.
Show relation values
Go to editor mode
Go to tab "Source"
Hover over relation column
Toggle ON to fetch actual relation values
Relation values are going to fetch and this can take while depend on database row size
Relation column has different icons
So that you can immediately recognise whether a relation column contains notion IDs or actual value. We have introduced to icons:
Relation column has Notion IDs
Relation column has actual relation content
Why do I have to do this?
Unfortunately, Notion does not immediately return the resolved relation names via the API. We have to read the data from the relation databases in a second step. As this process requires a long loading time or update time, we have decided in favour of this method. In some cases it can improve the loading speed by up to 80%. It is therefore always important to ensure that only the relation columns that are actually used are activated or deactivated.
Do I have to do this for every chart?
No, it is a global data jumbo setting, which is fixed to the explicit Notion database.
This means that if I have activated the column relation "Sales" in Chart 1, the relation column "Sales" will also be activated when I open Chart 2. No matter on which chart this is activated or deactivated, it is the same everywhere.
Feature Outlook
Of course, we don't want to stop here. We want to automate this behaviour in the future. This means that as soon as you use a relation column in your chart, we will automatically recognise this and load the data accordingly, as well as when the column is no longer used. We will inform you as soon as we have more information.
Updated on: 10/05/2024
Thank you!