Help

Save the date! Join us on October 16 for our Product Ops launch event. Register here.

Re: Interface button to create a new table

Solved
Jump to Solution
312 0
cancel
Showing results for 
Search instead for 
Did you mean: 
chris102
4 - Data Explorer
4 - Data Explorer

Hi,

I'd like to give users a button to create a new table in the backend with default fields and table name. This table could be a duplicate of an existing table. Is is possible to implement this functionality on the front end?

1 Solution

Accepted Solutions
kuovonne
18 - Pluto
18 - Pluto

While technically possible with an automation script and use of the web API, this is not realistic. In general, interface users should not be creating new tables. The interface user could not even access the new table from the interface because there would be no interface page for the new table. Setting up a database can be very different from setting up a spreadsheet.

Since you say that the new table would be a duplicate of an existing table, I suggest that you look into different ways of filtering records in a single table. I'm guessing that you should look into a system with linked tables: one table with the regular data, and another linked table with a record for each set of records that you would want in a different table.

See Solution in Thread

2 Replies 2
kuovonne
18 - Pluto
18 - Pluto

While technically possible with an automation script and use of the web API, this is not realistic. In general, interface users should not be creating new tables. The interface user could not even access the new table from the interface because there would be no interface page for the new table. Setting up a database can be very different from setting up a spreadsheet.

Since you say that the new table would be a duplicate of an existing table, I suggest that you look into different ways of filtering records in a single table. I'm guessing that you should look into a system with linked tables: one table with the regular data, and another linked table with a record for each set of records that you would want in a different table.

chris102
4 - Data Explorer
4 - Data Explorer

Thanks. Looks like this is not the intended use case for AT.

The intention here is to create a means of version control and history for data. Where each new table added by a user is a version (3D data structure controlled by the user). As you suggest, might need to look at doing this in a single table and use filtering.