Help

The Community will be temporarily unavailable starting on Friday February 28. We’ll be back as soon as we can! To learn more, check out our Announcements blog post.

Dependencies misreporting

681 2
cancel
Showing results for 
Search instead for 
Did you mean: 
matt_stewart1
7 - App Architect
7 - App Architect

Trying to do some base cleanup and design, and having trouble with dependency reporting.

 

Table A has Field A

Table B has Field B (Field A Lookup)

On Table A, when viewing dependencies of Field A, it shows one dependency listed, which is as expected the Table B's Field B. It also notes in small text that 9 dependencies rely on Field B.

On Table B, when viewing dependencies of Field B, it shows zero dependencies listed.

 

So what is the disconnect here? Are there 9 dependencies on Field B or is it 0? If i delete Field B i get NO notifications/warnings, but im not sure if im breaking something somewhere else and wont know until i happen to come across it.

How to troubleshoot and resolve this as its not just 1 field doing this, its regularly happening all over the place where the dependencies reported do not align.

 

 

 

2 Replies 2
Saravanan_009
8 - Airtable Astronomer
8 - Airtable Astronomer

It sounds like you're encountering a discrepancy in how Airtable is reporting dependencies between fields across different tables. This can be confusing and potentially problematic, especially during base cleanup and redesign.

correct... is there a fix? is this a big? is there something that would indicate which is correct?