Sorry to hear you’re having so much trouble. I [personally] have had no issues integrating Adalo with Airtable. The only issues I’ve run into are generally where the integrators [themselves] are inexperienced in design architectures or where the vendors are inexperienced with the details of the connecting services. Often these vendors attempt to create an environment that is intended to eliminate deep integration skills and experience only to create some very frustrating times for their customers who are given false expectations by the solution vendors.
To be clear, I doubt this issue is (a) an Airtable problem, or (b) solvable by Airtable themselves. The issue as you’ve described it is with Adalo which is unable to make assertions about missing field values in API results.
This is precisely how most APIs work. What you’re seeing is probably not a deficiency in Airtable or its API. It’s likely the Adalo connector assuming that the first time it saw data from Airtable, it decided that this was the data model and will be unable to see all fields, even those subsequently populated in Airtable.
There are other possible issues as well – for example the Adalo interface itself. One would have to look at this closely to determine the true cause of your calamity.
My recommendation - which sounds self-serving, but it’s not - is to hire a consultant to sort out this issue and advise you going forward.