# Data API - database fields with old names **URL:** \ **Category:** Tips\ **Created:** [August 18, 2025, 7:46am UTC](https://forum.bubble.io/t/data-api-database-fields-with-old-names/378828 "2025-08-18T07:46:08Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![michal.friedrich](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/michal.friedrich/32/245543_2.png) [@michal.friedrich](https://forum.bubble.io/u/michal.friedrich)\ **Post date:** [August 18, 2025, 7:46am UTC](https://forum.bubble.io/t/data-api-database-fields-with-old-names/378828/1 "2025-08-18T07:46:08Z")
Case: You call your data API and do not see data for filled out fields in your database records. You have changed some of the fields name - ex. from date\_XXX to certifiacate\_XXX\_date Solution: Check if the fields do not appear in their old names. I have no idea why this happens, but got a case like this. Confirmed by bubble support. Hope it helps you have less grey hair on your heads. ---
**Author:** ![georgecollier](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/georgecollier/32/182327_2.png) [@georgecollier](https://forum.bubble.io/u/georgecollier)\ **Post date:** [August 18, 2025, 8:05am UTC](https://forum.bubble.io/t/data-api-database-fields-with-old-names/378828/2 "2025-08-18T08:05:46Z")
Fields are displayed by their static IDs which are set when you first created them. This helps with backwards collapsibility as when you update the field’s display name, it won’t break any Data API connections. You can use the display by checking ‘use field display instead of ID’ in the API settings. ---
**Author:** ![michal.friedrich](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/michal.friedrich/32/245543_2.png) [@michal.friedrich](https://forum.bubble.io/u/michal.friedrich)\ **Post date:** [August 18, 2025, 8:18am UTC](https://forum.bubble.io/t/data-api-database-fields-with-old-names/378828/3 "2025-08-18T08:18:35Z")
You are 100% right. Damn, I thought I can share a nice tip. But using this options now is risky as when I toggle it my datalake will drown ☹ wish I knew about this field earlier, before integrating. Thanks for the tip!