Permission issues when creating new select options

Hi,

There is a similar topic here, it may help you.

But it doesn’t explain why it was previously working for you.

BR,

PBI

this looks incorrectly double-quoted for some reason.

Welcome to the callin.io community!

1. Screenshots of module fields and filters

Please share screenshots of relevant module fields and filters in question? It would really help other community members to see what you’re looking at.

You can upload images here using the Upload icon in the text editor:

2. Scenario blueprint

Please export the scenario blueprint file to allow others to view the mappings and settings. At the bottom of the scenario editor, you can click on the three dots to find the Export Blueprint menu item.

^{(Note: Exporting your scenario will not include private information or keys to your connections)}

Uploading it here will look like this:

blueprint.json (12.3 KB)

3. And most importantly, Output bundles

Please provide the output bundles of the modules by running the scenario, then click the white speech bubble on the top-right of each module, save the bundle contents in your text editor as a bundle.json file, and upload it here into this discussion thread.

Providing the output bundles will allow others to replicate what is going on in the scenario even if they do not use the external service.

Following these steps will allow others to assist you here. Thanks!

Please provide the rewritten markdown content *it should be in the markdown format.

It appears that the default Airtable modules no longer support adding new options to Single select and Multi select fields. This is a preventative measure to avoid populating your selection fields with unintended options.

This behavior is related to the “Typecast” option and can be an issue when creating or updating options.

While we await an update to the Airtable app (please vote for this feature request) that includes an advanced option to enable typecasting, here are two workarounds:

1. Reconstruct your Airtable call using the “Make an API Call” module.
2. Set the typecast option within the callin.io module's code:

• Duplicate the Airtable create/update/upsert module (right-click > copy).
• Paste the code into a text editor (any plain text editor will work).
• Locate the “typecast” option (it's usually within the first 20 lines).
• Change the value from “false” to “true”.
• Select all the modified code and copy it.
• Paste the copied code back into your scenario. This will create a copy of the original module with the typecast option set to true.

I typically place this behind an error handler to perform additional checks before creating the new option.

P.S. If you're seeing this, please also cast your vote for the option to be added to the callin.io Airtable app (link provided above).

A more straightforward approach to resolve this is to retrieve the data via the webhook. Subsequently, utilize multiple 'Get a Record' modules to fetch the record ID. Following this, extract the data using the Record ID. This method allows you to process the incoming data from the webhook as individual bundles.

Can you please elaborate? I don't understand how your example creates a record in Airtable with a select option that isn't already present in Airtable. I only observe Get modules.

Please provide more details.