From database IDs to data source IDs: what’s changing, why it matters, and how to upgrade in minutes

I’m thrilled to share that Blocky now fully supports the Notion Data Sources API.
If you build charts and widgets with Blocky, this change brings a
cleaner data model, a clearer creation flow, and soon powerful multi-source analytics.

As Notion evolves its underlying database architecture, the new Data Sources concept
brings precision to how tables are defined and referenced. That’s great news for reliability,
performance, and future features. It also means I’ve updated how Blocky connects, migrates,
and displays your content—so you don’t miss a beat.

What changed in Notion’s data model?

Notion now treats data sources as the individual tables that live under a database container.
Where you once targeted a database to reach its table, you now reference a data source ID
for exactness. In practice, pages are still rows, properties still define schema, and your
workspace keeps working—only with clearer boundaries across tables.

This shift is formalized in Notion’s latest API release. The 2025-09-03 version introduces
endpoints and behaviors tailored to data sources. For developers and integrations like Blocky,
that unlocks better schema control and more precise querying. If you’ve felt limited by loosely
scoped database references, this is the upgrade you’ve wanted.

What this means inside Blocky (creation, legacy behavior, defaults)

When you create a new chart or widget in Blocky, you’ll now be asked to select a data
source instead of only a database. This keeps your selection unambiguous—especially in
workspaces where one database now contains multiple sources.

Have older widgets built from a database ID? You’re covered. Blocky automatically maps
those legacy widgets to the first data source in that database by default. If your widget
was originally built from that first source’s schema, everything continues to work as before.
If you need a different source, you can quickly migrate with a refresh or click edit.

How to migrate existing widgets (three quick paths)

1. Refresh in the Blocky dashboard.
   Click the ellipsis, hit Refresh, and Blocky will remap the legacy database ID to the
   first data source automatically. If that’s the table you intended, you’re done.

2. Use Quick Actions in Notion (subscribers).
   If you’re on a Blocky subscription, you’ll see in Notion Quick Actions (ellipsis) a refresh option that also
   triggers a migration for the selected widget. It’s a fast path when you’re already working
   inside Notion.

3. Edit and save the widget.
   Choose Edit, review the selected data source (the first source is chosen by default
   for legacy items), and Save. If you need a different source, pick it from the list
   and confirm. Your chart or widget will immediately reference the new ID.

FAQs & edge cases you asked me about

What if my database now has multiple data sources?
Blocky defaults legacy widgets to the first data source. If that’s not the right one,
just open the widget, pick the correct source, and save. Future creations will ask you to
choose explicitly, so you’ll never land on the wrong table again.

Will anything break if I do nothing?
If your original widget used what is now the first data source, you’re fine. If not, the widget
may look off due to schema differences if open the editor again. A quick reselection fixes it. Also ensure your Notion
integration still has access to all related resources—especially for relations and rollups.

Editor errors when I try to edit
If the editor errors either because the data source is missing or the schema is different,
in the ellipsis menu there's and option to generate a widget code. This will copy all the customizations
and settings you done to the widget to the clipboard. You can then delete the original widget
and make a new widget and import the code inside the editor.

Permissions, sharing, and relations (read this if you see errors)

If a chart uses relations to another table, make sure your Notion integration is shared
with that related database. Without permission, relation or rollup properties can’t resolve,
and you’ll see partial or empty data in Blocky. Share access in Notion and refresh.

If you rotate workspaces, rename sources, or move them, confirm that the integration remains
shared. In Notion, you can Manage data sources from the database menu to move or adjust
sources as needed. Then come back to Blocky and refresh your widget to resync cleanly.

Developer notes: IDs, endpoints, and version changes

If you previously scripted around the old List Databases endpoint, note that it was
deprecated long ago and removed in newer API versions. The supported path is to use the
Search API to discover content and then operate with database or data source-specific
endpoints. For Data Sources, follow the latest reference.

You’ll also see new semantics around updates. Properties that belong to a data source are
updated via the Update a data source endpoint, while database attributes (like title or
icon) still use Update a database. If your automations distinguish between schema and
container metadata, your code will be cleaner than ever.

Roadmap: multi-source charts and multi-view options

This new API standard opens the door to multi-source charts in Blocky—think blending a
“Tasks” data source with a “Projects” data source in a single visualization. I’m designing
interfaces that let you compose series from multiple sources without the usual copy/paste grind.

I’m also building multi-view chart options so you can flip between bar, line, and area
views on the same dataset. That means faster comparisons, richer dashboards, and fewer clones.
If you’ve got specific combos you want to see first, tell me—your input will shape the rollout.

How to create a new chart with data sources (quick start)

• Go to Blocky and create a new chart or new widget.
• Connect your Notion account.
• When prompted, select a data source. You’ll see the exact table you want, not just a database.
• Pick your fields, choose a chart type, and click Save.
• Embed your widget anywhere you need it in Notion. That’s it.

If you’re curious about the underlying model, read Notion’s Data Source object docs and the
Working with databases guide for a crisp mental picture. Links below help you dive deeper,
while Blocky handles the heavy lifting and keeps your setup future-proof.

Helpful links (Notion & docs every builder should bookmark)

• Notion Developers — API home: Notion API
• Data Source object — schema & fields: Data source
• Update a data source — edit properties: Update a data source
• Working with databases — concepts & guides: Working with databases
• Changelog — deprecations & versions: Notion API changelog
• Blocky — charts & widgets for Notion: Blocky

Next steps (your quick checklist)

• Create a new chart with a selected data source.
• Refresh legacy widgets or use Quick Actions to migrate.
• Verify Notion permissions for related databases and rollups.
• Watch for multi-source and multi-view feature announcements on Blocky.
• Share feedback—what visualizations should come first?

If you run a team workspace, document the new “data source first” approach in your internal
playbook and link to Notion’s docs so everyone stays aligned. Your future self will thank you.

Other Articles

• Create Flashcards From Notion
• How To Embed
• Connect Blocky To Notion
• How To Create Widget Codes
• Request A Widget