Thanks @flusk - yep we solved it, it’s because that’s a ‘lookup’ field in AirTable, so we had to create a separate local field mapping to it.
Thank you!
Thanks @flusk - yep we solved it, it’s because that’s a ‘lookup’ field in AirTable, so we had to create a separate local field mapping to it.
Thank you!