Airtable fields - create vs update

:bullseye: What is your goal?

Create records in Airtable with certain fields populated

:thinking: What is the problem & what have you tried?

see below

:clipboard: Error messages or input/output bundles

I have a scenario that watches Shopify for new orders. When an order comes in, an Iterator is applied to the contents of the order to make Airtable records for each order line. I’m seeing that the fields available to the Create a Record module is limited. When I follow this module with an Update a Record, there are many more fields available. The Update module uses the exact same connection as the Create module, and both have been refreshed. Why can’t I just do it all in the Create records step?

Hi Mark, welcome

That’s normal behavior. The Create a record module only shows fields that Airtable allows at creation time. Some fields (formulas, rollups, lookups, read-only, linked logic, etc.) won’t appear there.

Once the record exists, the Update a record module can access more fields, which is why you see them there. So the create-then-update pattern you’re using is actually the right way to do it.

Nothing wrong with your setup. It’s just how Airtable works.

Regards, Tony

1 Like