A new "filtered" table from existing table

Hi,
I searched through the topics, but couldn’t find a solution for what I want.

I have a table with exported data. It contains all the invoices of a year. This table will be updated regularly.
I want to give out data for people, but not everything. I want to provide them a separate table(not a view) which is already filtered, by one of the columns (project number). This way source data remains intact and people could have their own table to work with. Table structure would remain as the source export table with all its columns. So its a filtered copy of that table.
I assume this is somehow possible in coda, but couldn’t figure it out yet

I would be pleased if someone could help me with this. Thank you!

oh… and ideally automated by pushing a button and not manually :slight_smile:

Hi @Konsztantinosz_Dulasz1 ,
and welcome to Coda Community!

Have a look at this example:

You then just need to create an automation that runs at a convenience schedule and that triggers the button.

I hope this helps.
Cheers!

4 Likes

Thanks @Federico.Stefanato
So I will need to set up an empty table first, with as many columns as in the source table and give them the same column names. I think this can work out this way for what I need it. Thank you!

1 Like

Correct.
If you want to have a completely detached solution.

Anytime!

@Federico.Stefanato
Thanks very much for your solution and comments above.

I appreciate there is a lot of info below, but we’re working on something similar and I’d be grateful for any help/thoughts/comments on how to use a similar set up with filtered/nested tables, all working in tandem with a master set of data.

We’d like to set up a company-wide target-management system that would allow all staff to see their profile (i.e. in the wider sense, a row in the company table/database) and add their targets (more detail on this below).

We’ll need to have hierarchical access so that the company directors can see the everyone’s progress and check in on each member of the senior leadership team’s progress, who in turn can do the same with the middle managers’ progress, who in turn can do the same with the staff they are directly responsible for, etc. etc. but no one should be able to see up the chain of access, as it were.

The targets will need to be controlled (i.e. selected from a list defined by the directors and leadership team) and will need to be categorised, the distribution/use of which will also need to be controlled (i.e. each member of staff will need to set at least one personal target, one administrative target and one organisational target, for example, but they should be able to choose from a selection of targets in each of those categories).

Again, thanks very much for your help in advance.

Hi @NexGen_IT ,
I’m happy the suggested solution was useful.

It sounds great that you are thinking of Coda for your solution!
However, your request seems to be quite wide, looking like a project management/OKR implementation that requires a rather complex level of permissions and roles…

Posts here are usually more targeted on narrowed, specific issues/solutions.

I’d suggest to start with something in the Gallery and evolve your use case from an existing one.

You might also consider to ask for some consultancy support here in the Community (there are really great experts here) to build-up your project according to your needs.

I hope this helps!
Cheers.

2 Likes