Skip to main content
Question

Custom Interface Extentions - Support for "table" type of custom

  • December 30, 2025
  • 3 replies
  • 83 views

Forum|alt.badge.img+2

Is it my impression or the latest version of the SDK removed support for defining a table as a custom parameter? My extension reads data from another table as support for that has been recently added. In order to avoid hardcoding things, I was allowing users to select a table. This was supported  (see link below). However, the latest version of the SDK does not seem to support that. (^0.0.0-experimental-e7419444f-20251120). I’ve updated my code so the parameter is now just a string. It seems to be working. Could you please confirm this makes sense?

https://airtable.com/developers/interface-extensions/api/BlockPageElementCustomProperty

The signature of the type BlockPageElementCustomProperty I’m getting does not include that type anymore (see below) and I also get a run time error.

type BlockPageElementCustomProperty = {
key: string;
label: string;
} & ({
type: 'boolean';
defaultValue: boolean;
} | {
type: 'string';
defaultValue?: string;
} | {
type: 'enum';
possibleValues: Array<{
value: string;
label: string;
}>;
defaultValue?: string;
} | {
type: 'field';
table: Table;
/** If not provided, all visible fields in the table will be shown in the dropdown. */
possibleValues?: Array<Field>;
defaultValue?: Field;
});


 

3 replies

GCheung
Forum|alt.badge.img+17
  • Community Manager
  • January 9, 2026

Hey, ​@WGomes​! ​Because your question hasn't yet received an answer/solution from the Community, we've created a Support Case on your behalf with our Airtable Expert Team to get you the quickest response possible. Please check your email for follow-up and your case reference number—and continue to follow this thread as new community members tend to share answers and add knowledgeable responses regularly. Thanks!


Forum|alt.badge.img+2
  • Author
  • New Participant
  • January 25, 2026

The issue above was caused by me adding a caret in front of the SDK version on my package.json. 

I had something like the below. Note the caret in front of the version number:
 "@airtable/blocks": "^0.0.0-experimental-e7419444f-20251120",

I wanted to load the version from Nov/20th or something newer, but due to how these experimental versions are numbered, this was telling NPM to actually loading an older one.

AFAIK, by newest, I think NPM means anything with the highest string value as long as is starts with ‘0.0.”. Looking at my package-lock.json, it was loading the version 0.0.0-experimental-f52bc4e5e-20250709 as "f52..." is higher than "e74...".  In other words, it was loading a version from July.

The fix it to remove the caret. The seemingly random hex value between “experimental” and the date throws NPM off and makes it install an older version.


Flow Digital
Forum|alt.badge.img+2
  • Participating Frequently
  • January 28, 2026

Hey ​@WGomes  

Glad the issue was resolved. Nice one!