![]() The scripting documentation for attachment fields does not reflect the new deprecation timeline for urls expiring. Will there eventually be a workspace model that will expose the workspace subscription level? 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |