I have been testing Seatable and I am impressed.
I have a question.
Let’s say I have a Base called Employees and another base called Salaries.
I want to replicate 2 columns (name,lastname) from the base “Employees” to the base “Salaries”.
So as soon as I enter a new employee in the first Base, it will automatically be added to the second base.
Hi Arjon, welcome to the Seafile Forum.
Pleased to hear that you are impressed!
Such replication is possible (will be possible soon). You can use something like Zapier. That’s the easy way. Another option is a script that you can run. For more infos on scripting in SeaTable, see the scripting manual.
I know what you mean, but neither links across bases nor automations are not available in SeaTable. Sorry!
This said: SeaTable is developing very fast! When I say “are not available”, you should hear “not yet available”.
If you are using self-hosted version, there is a feature called “common dataset” that can sync part of a base to another base. You can first publish a view in base 1 as a common dataset, then import it in base 2. After imported, there is a button for you to perform a manual sync when base 1 is updated.
In our own use case, we publish employee information as a common dataset. Some users publish customer list as a common dataset to be used in multiple bases.
In a group that has permission to the common dataset, open a base and create a new table: normally when you create a new table, you only have two options: create an empty table, or import a CSV. But here, you’ll have a third option: Import common dataset:
After it’s imported, the table menu of this one will have the entry “Sync”:
As we haven’t enabled common dataset on cloud.seatable.io yet, we don’t have this part of the API documentation yet.
But our partner in China has it in their API documentation, fortunately it’s also in English: Seafile Server
I shall encourage you to give it a try in your own instance!
Last but not least, for anyone who’s interested in the SeaTable API, our API documentations are here (not complete yet, but we’re 85% finished):