My desire is to have a column that gives me different options depending on another column selection. Is this possible?
Hey @Fred_Butson
first of all, great video explanation! Super clear to understand what you mean 
That’s actually a very interesting question . Usually you only have one data type/schema (or whatever it is called?) per column, like in a database. That is how Coda works and mixing it up is not that easy by intention. You are able to copy and paste “wrong” objects in a lookup, or also if you change the lookup formula, the existing elements should not be removed - but that is not what you acutally want and you can also not access the values of the “wrong” object. But it wouldn’t be Coda, if there is not some way around.
You could just use one table for all job levels, add all possible columns and hide them in the different views of the same table. Then use a select list and filter the options by the given Level Type. But then on hover, you will also see the empty columns of other level types, which you don’t want. (I’d probably still consider that way if it would be my doc.)
But here is a solution where I’m mixing up apples with pears, in two tables, selectable depending on type:
-
make a select list populated by a table depending on your type/name
This will give you the select list where you can select only the right objects - and on hover it shows only the columns of that tables -
if you want to access the object, it gets a bit tricky. You can not just say “object.colour” because Coda blocks this, as soon as two different tables / object schemas are involved. But you can use a switch again to filter the right table and get the property:
Here the doc to play around:
Hope that helps!
3 Likes
Thank you! These are two great options. I really do appreciate the assistance.
1 Like
Hey @Fred_Butson,
how about changing a little bit your data model?
If you need to have a structural consistency, you can generalize to an higher level (avoiding declarative polymorphism on your formulas).
Please, have a look at this example:
I tried to sum-up all the main requirements:
- decoupling compensation and profile description (so that different people work on different data)
- keep consistency in types and levels
This would also allow to automatically “generate” the full matrix of competencies.
The only drawback, is that this is a sparse matrix (not all criteria are for all levels), but if you can live with that, everything else is consistent.
Let me know if this helps.
Cheers!
3 Likes
@Federico.Stefanato - Could you give insight into how to automatically “generate” the full matrix? I’ve got all the other tables rolling at this point. Love the assistance by the way. At least from the doc you linked I am not seeing any formulas in the Matrix.
Got it. It’s just the competencies table viewed by groupings. It got it. Thanks again.
Sorry @Fred_Butson ,
It was just a hint.
Actually I was thinking of a button that generates the matrix based on the provided structure.
The matrix view it’s just a matter of grouping, but the table itself can be generated.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.