In the last couple days Coda have changed the way Cross-Doc works, and as far as i’m aware did not tell anyone!?
To date (and since the last big cross-doc update), the cross-doc version of a table was filtered based on the criteria set in the “Manage Sync Filters & Columns” window in the Cross-Doc options in the destination doc.
Now as of two days ago, the filtering on the master version of the table in the source doc now dictates the available rows to filter in the “Manage Sync Filters & Columns” window.
I’m pretty frustrated as this seriously disrupted many of our docs. I presume others are experiencing this too, do we know whether this will be temporary or permanent?
I have had a few other more minor instances of ‘new behaviour’ or bugs in the last couple weeks and I do find myself wondering whether there’s suddenly a different approach being taken by the devs since the merger/acquisition…?
I understand your frustration. I haven’t checked, but generally speaking I would recommend keeping your ‘source’ tables as ‘clean’ as possible (no filters). If you need filters in your main doc, filter a view and not the main table.
Even if this behavior has changed (and I agree, we should be informed about that type of changes), it should be a pretty straightforward process to make it work again. First, copy your filtered table at the page where you use it right now, then move the source to a hidden page and remove the filter - and you should be done.
Ah thank you for the reminder, now I recall why I oft had the master tables filtered or with fields hidden - where hovering is influential it really does make a difference.
This is what was so frustrating here - The Cross-doc changes/improvements detached the syncing criteria from the source master table, and now they’re seemingly in part coming back