@oleg We are using the Table ID becuse in the API “Names are discouraged because they’re easily prone to being changed by users. If you’re using a name, be sure to URI-encode it.”
We are looking for a suitable platform like Coda to implement/extend some app/widget based solutions.
At this stage we are doing some logical and functional prototyping to explore what’s possible.
Use Case: An external app stores data in a Coda Table.
- The Coda API does not support creating or editing Tables or Columns, or managing them.
- On that basis, we are creating a Doc Template that includes a predefined Table. (See other idea)
- We have a formula that combines the App Url with the DocID and TableID as arguments
- A user can use this Url to embed the app in Coda so that it is connected with the target Table.
There are some obvious limitations and risks with this approach:
API performance, reliability and capability
It requires clumsy user action and can be broken
Conflicting changes when Table and App are udated simultaneously by different users (Option: Upgrade to Team Page Locking to avoid this and Cross-doc to replicate in another location).
Thanks for your interest! Any update on API 2.0, relevant roadmap items, feedback or ideas you have would be greatly appreciated