# Updates to dynamic page source in CMS pages API

**URL:** <https://community.hubspot.com/t/updates-to-dynamic-page-source-in-cms-pages-api/43453>\
**Category:** Developer Announcements\
**Tags:** api, announcement\
**Created:** [September 7, 2021, 3:29pm UTC](https://community.hubspot.com/t/updates-to-dynamic-page-source-in-cms-pages-api/43453 "2021-09-07T15:29:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmclaren](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jmclaren/32/38449_2.png) [@jmclaren](https://community.hubspot.com/u/jmclaren)\
**Post date:** [September 7, 2021, 3:29pm UTC](https://community.hubspot.com/t/updates-to-dynamic-page-source-in-cms-pages-api/43453/1 "2021-09-07T15:29:17Z")

</div>

We recently [made it possible to create dynamic pages powered by CRM objects](https://developers.hubspot.com/changelog/dynamic-pages-powered-by-crm-objects-are-now-live). Prior to this only HubDB was able to be used as a data source for dynamic pages.

To add support for the additional source type we created 2 new properties (`dynamicPageDataSourceId`, and `dynamicPageDataSourceType`). We intended for this change to be non-breaking and would handle any API requests involving the old `dynamic_page_hubdb_table_id` by setting the values of `dynamic_page_data_source_id`, and `dynamic_page_data_source_type` automatically.

This works correctly for POST requests - to create new pages. Unfortunately for [PUT requests - used to update existing pages](https://legacydocs.hubspot.com/docs/methods/pages/put_pages_page_id) - if a developer only passes the `dynamic_page_hubdb_table_id` the data source will not be updated.

Because this only affects updates to existing pages, the number of affected accounts and requests is very low, but we wanted to provide guidance.

From now on you should not use `dynamic_page_hubdb_table_id` in your API calls. Use `dynamic_page_data_source_id` and `dynamic_page_data_source_type instead.`

To keep backward compatibility, we will continue to return `dynamic_page_hubdb_table_id` in GET requests in the V2 API. Additionally we will continue to automatically upgrade POST requests made with `dynamic_page_hubdb_table_id`. When the V3 API is released, it will not support `dynamic_page_hubdb_table_id`.  
If you have any questions please ask below.