Hi Coda community,
We are trying to build a solution to share Dashboard with our clients. We have several global docs olding data such as list of equipments, Wiki linked to those equipments, and so on.
We have one “Dashboard” doc per client olding all the client information (what equipment we installed for them, their specific data (MAC, IP, SN, HOSTNAME,…) and so on.
We would like to share our wiki with our client but to only show them the WIKI’s linked to equipments relevant to them. I was expecting to be able to filter CROSS-DOC wiki table to only sync equipement that are find .in(DB_ITEM) witch are the equipment installed for that specific client (a table in the “Dashboard” doc).
When trying to filter the CROSS-DOC wiki, it seems the filter only show me metadata of the original Wiki doc but nothing related to the destination “Dashboard” doc, preventing me to filter this correctly. We could of course filter what is shown on the destination Doc but it would make sense to filter before importing rather than after. Our wiki will go over 10.000+ lignes at some point and this will then break.
Anyone as any idea if this is possible or what could be the solution after reaching the 10k crossdoc limitation ?
Many thanks for your help.
1 Like
hi @Yannick_Pinta ,
so far we know that the 10.000 limit remains for cross docs, but if your source doc has 80K rows and you have 8 clients, each can have 10K rows.
you can use a webhook pack to bypass this 10k row limitation.
I hope it helps, Christiaan
3 Likes
Thanks for your answer Christiaan. Does it mean, filtering as I ask is not possible ? Using Webhook is a realy good idea, but it will make things really complex because I still need to push the data back and forth in order for coda to know which equipment has been installed for which client and then what wiki to sync accordingly. I believe I could use webhook from the Dashboard docs to add the client name to a list in the equipment table and then filter the cross-doc searching for that name in the crossdoc filter but it is far from being easily scalable. I might work though 
Cheers for the idea ! If any body as a better one, I’m all hears 
1 Like
hi @Yannick_Pinta ,
well, to avoid the 10K limit a webhook is a way out and I plan to add documentation later this year to the pack to demonstrate how to apply a two way sync, but as you noticed, although possible, it is not something that works simple.
regarding the filter, you can set up a row and column filter on your source table to only push data to your target table as you see fit, it is a manuel process via the settings of your cross doc. In a web hook logic you could handle this via an extra table, but again you invite complexitiy to the table, who is rarely a nice guest to have around.
there is no real clever solution for now, i hope the coda team makes it work in the year to come!
cheers, christiaan
3 Likes
Hello Christaan, many thanks for your answer. I’ll be very interested by extra documentation about how to implement this pack. Cheers for your inspiring help to the coda community 
2 Likes