Will there eventually be a workspace model that will expose the workspace subscription level?
Airtable api skd license#
This will let me license my apps on a per workspace level.
I currently license my apps on a per base level. You don’t need to waste any resources answering this question.Įxposing the workspace ID to the base in custom apps opens up some interesting possibilities. But it is just academic curiosity because I know that there is no practical reason for that to happen. I’m a little curious what happens if the name of one field matches the field ID of a different field. Check out the APPs API documentation and Scripting API documentation to learn more about using this method.įeel free to drop any questions or comments below!īeing able to use field IDs in the REST API is wonderful. Naming things is hard, hopefully this makes it a lot easier.
Airtable api skd update#
Use the updateNameAsync method to update any field name from the SDK or a scripting block. Check out the blocks sdk documentation for more comprehensive syntax.įield.updateNameAsync method to SDK and Scripting You can access the ID of the workspace that your base is in the blocks SDK by calling on the base.workspaceId property. That way, you can avoid modifications to your API request even if the name of the field or table changes. Now you have the option to provide field and table ids in your API requests, and receive ids instead of names in the response. IDs and names can be used interchangeably in API requests.
The create record and delete record sections of the docs inform you if they are unavailable because the table is a synced table.Fields in synced tables that cannot be edited are appropriately marked in the fields section of the docs.To make these restrictions clearer we’ve updated the api docs so that These restrictions, such as being unable to add new records, are also present in the API. Synced tables are one of the most powerful tools in Airtable but are less editable than regular tables. We hope this saves you the headache of dealing with unexpected field name changes in the future. To make this more prominent, we just added the field id in the fields section of the API docs along with a blurb explaining that field names and field ids are interchangeable. We recently made a bunch of improvements to our API, SDK, and documentation! Check out the list of changes below.ĭid you know that field ids and field names are interchangeable? Using only field names can be problematic when there are unexpected field name changes.
0 kommentar(er)
