# Way to check currently used fields

**URL:** <https://community.fibery.io/t/way-to-check-currently-used-fields/9244>\
**Category:** Get Help\
**Created:** [July 20, 2025, 11:36pm UTC](https://community.fibery.io/t/way-to-check-currently-used-fields/9244 "2025-07-20T23:36:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Post date:** [July 20, 2025, 11:36pm UTC](https://community.fibery.io/t/way-to-check-currently-used-fields/9244/1 "2025-07-20T23:36:43Z")

</div>

I have a lot of views which use a field that is being deprecated. The data has been migrated into another format and I need to be able to delete the original so that it doesn’t get used.

If possible, I need to know what views and filters are looking at the old field so I can manually change it to look at the new one, and then be assured that my delete will not have unintended consequences.

---

<div class="post-metadata">

**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\
**Post date:** [September 7, 2025, 5:43pm UTC](https://community.fibery.io/t/way-to-check-currently-used-fields/9244/2 "2025-09-07T17:43:20Z")

</div>

Hey there, this one looks like could be a very useful feature for admins. Have you already filed a feature request?

I found no means for that and immediately thought of Fibery API. But this isn’t something trivial.

**From Fibery AI:**

Recommendation

For now, the manual approach is more practical because:

1. API complexity: Requires significant reverse-engineering effort

2. Undocumented structures: View metadata formats aren’t documented

3. Maintenance burden: Internal formats may change without notice

If you need automated field dependency tracking, consider:

1. Feature request: Ask Fibery team to add native field dependency tracking

2. Hybrid approach: Use APIs for basic analysis, manual verification for critical changes

3. Community collaboration: Work with other developers to document the metadata structures

The APIs provide the raw data needed, but building a comprehensive field usage tracker would be a substantial development effort due to the lack of detailed documentation about internal data structures.