Hello everyone,
I read in this thread: Bringing conditional format to cross-doc synced tables
That conditional formatting does not get pushed by cross doc. Thats fine and I appreciate that it might be difficult to add that as a feature super fast.
What I would love though is to add a button to condition formatting that says something like “copy all formatting”. That way when I’m setting up my client dashboards its a much quicker process to just copy and paste all formatting to that table. Rather than having to go through each one which is a lengthy process!!
I appreciate that if the data isnt setup correctly on the other side then you may see some broken formatting. Thats fine with me as it takes 2 seconds to delete the broken ones rather than the 5-10 mins it takes to setup the conditional formats from scratch!
Seconding this request!
Most of the tables we want to cross-doc have extensive conditional formatting. This would massively accelerate deployment of our cross-doc plans!
YESssssss such a great idea
Just wanted to bump this up. 2 years later this is still my #1 request for Superhuman Docs!
Hi @Harry_Doull
You can read, create, and delete conditional formatting using the Superhuman MCP.
The Superhuman MCP includes several tools that enable actions you cannot normally perform in Coda using formulas/actions or the API, such as showing and hiding columns in a table, renaming column names, renaming views/tables, and managing conditional formatting.
It’s worth taking a look at the available tools.
To copy conditional formatting from one table to another, you can use a prompt like this in your preferred LLM with the MCP connected.
Copy all conditional formatting rules from the source table to the destination table.
Source: [SOURCE TABLE/VIEW URL]
Destination: [DESTINATION TABLE/VIEW URL]
Steps:
1. Read the source view's conditional formats (conditions, colors, text styles, scope).
2. Read the destination table's columns and map every column reference in the source conditions and scopes to the matching destination column. Match by name first, then by type and role (e.g., display column). Rewrite each condition using the destination's column IDs.
3. Before writing anything, show me the mapping (source column → destination column) and flag any reference you couldn't map with confidence. Ask me about anything unclear: missing columns, ambiguous matches, or formulas that reference other tables.
4. Once I confirm, create the rules on the destination view, then read the view back and verify that each rule's condition, colors and scope were saved correctly. If a rule saved blank or incomplete, update it by its ruleId.
5. If a style can't be reproduced exactly (e.g., the API rejects identical text and background colors), apply the closest version and tell me what differs.
Best,
Felipe Arnhold from SimplaDocs
