I don’t think it is a copy-paste error. The quotes look correct in the screen shot. The color coding in the screen shot also make me thing it is not a problem with quote type. (@Bill.French, I’m curious how much you’d wager, but I’m not the gambling type or I would already have a fine sandwich.)
The text is also copy/pasted from the documentation (which cleverly adapts to the base, including whatever input variables are created). When Airtable created this documentation, the programmers took care to make sure that the code could be copy/pasted (note the “copy” button in the corner of the documentation.
The fact that the documentation is copied also makes it highly unlikely that it is a spelling error, or that there are stray/hidden space characters in the input variable name. I would still like to see what a console.log of inputConfig by itself would be, but I suspect that it would be an empty object.
It also isn’t clear what the comment “the code won’t run” means. For example, is the “Test” button disabled? Or is the “Test” button enabled, but there is no obvious output when the button is run? Or is the automation on, but not getting triggered? Or is the automation on and triggering, but throwing an error?
I bet that the error reported in the initial post comes from the code editor–not from actually running the script. I sometimes get the wavy red underlines on code that I know will work, and the code editor has recently been more zealous in handing out wavy red underlines, so I don’t always trust them to be actual problems.
The screen capture also has a slightly different icon with the value for the input variable from what my screen shows. This may be just a matter low resolution in the screen shot, or it may indicate that we somehow have different versions of code running.
I’ll run the risk of offending again, and suggest my troubleshooting tips, as basic as they are …
-
Try console.log() of the variable that isn’t giving the expected value. If that doesn’t work, try console.log of an earlier variable. In this case, if console.log of one of the properties of inputConfig doesn’t give the expected result, try console.log of the variable itself.
-
Retest every previous part of the automation, including the trigger. Make sure that the test of all the previous steps are successful.
-
Restart Airtable / restart the computer. While it is restarting, have a snack, a drink, and possibly a nap. I’m always surprised when having a snack, a drink, and a nap solve my coding problems, but they have on multiple occasions (even when the drink isn’t alcoholic).
