# Noloco won't read Airtable Lookup field, if Lookup has conditional logic **URL:** \ **Category:** Bugs\ **Created:** [October 2, 2024, 5:35pm UTC](https://community.noloco.io/t/noloco-wont-read-airtable-lookup-field-if-lookup-has-conditional-logic/1289 "2024-10-02T17:35:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![dianakirby](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/dianakirby/32/38_2.png) [@dianakirby](https://community.noloco.io/u/dianakirby)\ **Post date:** [October 2, 2024, 5:35pm UTC](https://community.noloco.io/t/noloco-wont-read-airtable-lookup-field-if-lookup-has-conditional-logic/1289/1 "2024-10-02T17:35:30Z")
When I’ve used Airtable’s Lookup field feature to set conditional logic (e.g. only show linked records that have xyz status) or Limit the number of items shown (often to 1st or last linked record)- Noloco won’t pass the data through. It shows up as blank. I assume because of the data that’s being passed through it won’t read to the text field in No ![Screenshot 2024-10-02 at 11.28.49 AM](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/1X/5ca7678ee3d689d8819c1aa724d93dd063dd1b9d.png) ![Screenshot 2024-10-02 at 11.28.58 AM](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/1X/7277e53d721a12f1b149c38f4ff59692e6e04354.png) ![Screenshot 2024-10-02 at 11.29.21 AM](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/1X/3b6ca98f659af957eeac042af98a8973bc217b1e.png) loco. So I added a second field in Airtable to have a formula field of the Lookup field’s input and that worked. Tried first to do all this in Noloco, but couldn’t set that capacity (conditional logic or only show first or last) within Noloco’s native Lookup field. ---
**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\ **Post date:** [October 2, 2024, 6:33pm UTC](https://community.noloco.io/t/noloco-wont-read-airtable-lookup-field-if-lookup-has-conditional-logic/1289/2 "2024-10-02T18:33:47Z")
Thanks for flagging this @dianakirby - coincidentally this was flagged by someone else just now. We should be able to try and recreate it and get to the bottom of it. ---
**Author:** ![dianakirby](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/dianakirby/32/38_2.png) [@dianakirby](https://community.noloco.io/u/dianakirby)\ **Post date:** [October 2, 2024, 6:52pm UTC](https://community.noloco.io/t/noloco-wont-read-airtable-lookup-field-if-lookup-has-conditional-logic/1289/3 "2024-10-02T18:52:05Z")
Ha what timing! I’d seen it a few weeks back as well where the same issue occurred but for a form. We were trying to create a NoLoCo form and used an Airtable lookup field to limit the data that can be seen in the field responses. And same problem. I knew we could limit the field responses in noloco’s form itself so I can’t remember now why we tried the Airtable field route instead. **Diana Kirby** Consultant & Designer (303) 406-0357 [weactualize.com](http://www.weactualize.com/) [Schedule a meeting with me](https://calendly.com/weactualize/consultation) ---
**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\ **Post date:** [October 31, 2024, 1:38pm UTC](https://community.noloco.io/t/noloco-wont-read-airtable-lookup-field-if-lookup-has-conditional-logic/1289/4 "2024-10-31T13:38:58Z")
Hey @dianakirby - sorry for the delay here, but this bug was more difficult to track down than expected. We believe we’ve deployed a solution, if you’d like to try it again. In short, your lookups with conditional logic should behave correctly now Thanks again for flagging it and letting us know