Skip to main content

Development & APIs

Need development and API help? Ask your questions here!

  • 3,668 Topics
  • 11,752 Replies
3668 Topics
F
F_terstalNew Participant
asked in Development & APIs
API update records doesn't work in postman.. created records does work and get records work to

HI, I read the document : https://airtable.com/appEYx9XUfEttr3Nr/api/docs#curl/table:table%201:update I just copy and past the code… and i get errors… but getting records or creating records it is working… I put the api_key as a parameter and in headers both doesn’t work for updating the records… In the header is put Content-Type: application/json https://api.airtable.com/v0/appEYx9XUfEttr3Nr/Table%201 { "records": [ { "id": "recwpwzgzp7pTHfMb", "fields": { "Name": "test", "Notes": "test" } }, { "id": "recjKjPPQqaXh60MH", "fields": { "Name": "test2", "Notes": "test2" } } ] } { “error”: { “type”: “INVALID_REQUEST_UNKNOWN”, “message”: “Invalid request: parameter validation failed. Check your request data.” } }

151
F
W
WidgeticKnown Participant
asked in Development & APIs
Too many re-renders

Hi all! I’m trying to read from two tables using useRecords which have a limited number of fields to create a stateful content variable which I have to pass on to the next react Component. Here’s my code const { translator, compId } = props; // Block viewport const viewport = useViewport(); const [editorVisible, setEditorVisible] = useState(false); const [content, setContent] = useState(demoContent[0].content); // Block settings button useSettingsButton(function () { if (viewport.isFullscreen) { setEditorVisible(!editorVisible); } else { viewport.enterFullscreenIfPossible(); setEditorVisible(true); } }); // read the current tables and translate the content to // 'content' object const contentTable = base.getTableByName("Content"); const detailsTable = base.getTableByName("Details"); const contents = useRecords(contentTable); const details = useRecords(detailsTable); const relevantDetail = details[0]; const myContent = conten

200
W
C
Charanjit_KaurNew Participant
posted in Development & APIs
S
Savalas_ColbertNew Participant
posted in Development & APIs
R
Rob_RoseNew Participant
posted in Development & APIs
P
Pjero_KusijanovKnown Participant
posted in Development & APIs
L
Leslie_MillerKnown Participant
asked in Development & APIs
C
Chris_GuthrieInspiring
asked in Development & APIs
S
Savalas_ColbertNew Participant
posted in Development & APIs
R
RnJInspiring
posted in Development & APIs
IOS app keeps crashing. Any performance updates coming?

I have a fairly large base (approx. - 20k records, 20 tables, 300 fields, hundreds of views, etc.) and I am no longer able to open the IOS Airtable app (keeps crashing). Also tried to open via desktop mode on iPhone10 browser but crashes too. I must currently use a desktop/laptop to access my base. My temporary workaround was going to be use a shared view/snapshot of the information that I always need when away from desktop/laptop (view only/no editing) which would limit the records down to the view of a few thousand records. That worked ok, however I can’t filter & sort the information using the mobile website. Tried switching to desktop mode, which would have worked great, but I can’t scroll the base up/down & left/right. Any performance updates coming to IOS App? OR ability to filter/sort on mobile website views? OR ability to scroll on IOS with browser in desktop mode? Thanks.

212
R
K
Keith_ArmstrongNew Participant
posted in Development & APIs
W
WidgeticKnown Participant
asked in Development & APIs
Cannot create table

Hi all! I’m trying to create a new table using base.unstable_createTableAsync following the example in the guide. This is the code I’m using - const fields = [{ name: "MyField", field: FieldType.SINGLE_LINE_TEXT }]; if (base.unstable_hasPermissionToCreateTable("MyTable", fields)) { await base.unstable_createTableAsync("MyTable", fields); // and create records } But I keep getting the error Uncaught (in promise) Error: Can't create table: invalid field config for field 'MyField'. Creating or updating options for undefined fields is not supported at this time. at Mutations._assertMutationIsValid (bundle.js:formatted:7299) at Mutations.applyMutationAsync$ (bundle.js:formatted:6813) at tryCatch (bundle.js:formatted:94903) at Generator.invoke [as _invoke] (bundle.js:formatted:95131) at Generator.prototype.<computed> [as next] (bundle.js:formatted:94956) at tryCatch (bundle.js:formatted:94903) at invoke (bundle.js:formatted:94997) at bundle.js:fo

160
W
S
Stephan_KardosNew Participant
posted in Development & APIs
M
Mike_YamatoNew Participant
posted in Development & APIs
S
Sidney_MLNew Participant
asked in Development & APIs
M
MixableNew Participant
asked in Development & APIs
C
Christian_RainwNew Participant
posted in Development & APIs
D
Dima_LkhagvatogNew Participant
posted in Development & APIs
Kamille_Parks11
Kamille_Parks11Brainy
asked in Development & APIs
No-Conflict Appointment Scheduler

Use Case: You have a table of stylists, therapists, technicians, etc. (“agents”) who perform any number of services, and customers are supposed to schedule an appointment with an agent to perform a service but only when that agent is available. While you think the No-Conflict Asset Reservations script is great, it doesn’t take into account your need to schedule an agent for more than one appointment per day. Solution: No-Conflict Appointment script by Kamille. An improvement upon my previous script, you can now schedule same-day appointments assuming those appointments don’t overlap. It allows users to select a service, pick a qualified agent/employee to perform that service, and then select upcoming dates and times which work for that agent. The script opts to use buttons as opposed to text box inputs to reduce human error in typing in correctly formatted date/time strings. Since there isn’t a datetime picker input type, I basically hacked my own using two conditional button inpu

665
A
M
MixableNew Participant
asked in Development & APIs
T
TuurInspiring
posted in Development & APIs
J
Josh_CooperInspiring
asked in Development & APIs
F
francisco_silv1Participating Frequently
posted in Development & APIs
T
Tommy_ChanParticipating Frequently
posted in Development & APIs
M
Matt_CarusoKnown Participant
posted in Development & APIs
Non-declarative namespaces error

I’m working on getting my dev environment ready to start working on a custom block. However, I’m running into an error. After running block run in Terminal and allowing my browser to load https://localhost:9000, opening the block in Airtable yields: /usr/local/lib/node_modules/@airtable/blocks-cli/transpiled/src/builder/node_modules/yaml/index.d.ts: Namespace not marked type-only declare. Non-declarative namespaces are only supported experimentally in Babel. To enable and review caveats see: https://babeljs.io/docs/en/babel-plugin-transform-typescript 107 | str: scalarOptions.Str 108 | } > 109 | export namespace scalarOptions { | ^^^^^^^^^^^^^ 110 | interface Binary { 111 | /** 112 | * The type of string literal used to stringify `!!binary` values. Any ideas as to how to start troubleshooting this? Admittedly, I work more with Python and this is my first dive into Node development.

93
S

Badge winners

Show all badges
Terms & ConditionsAccessibility statement