Restructure a Button currently using SwitchIf to create variations of a big tracker table

2

:waving_hand:t2: @Libby_Riefler

watched your loom a few times and without really diving under the hood and looking at your doc setup and structure, here are a few tips that may help…

  1. Utilizing Button() formula - usually i will use this to switch out hard coded buttons in a SwitchIf or If situation. Note - using Button() formula will create an error message dialog popup “Formula calculated column. Values can’t be directly edited.Edit column formula” if clicked twice in succession.
  2. With the lag you’re noticing - is this when
    1. Changing things in the formula panel i.e. when updating the broken links/placeholder of the user- You can type “false“ at the very top of the formula panel while updating it and it will make changing the formulas easier/faster. Then delete the false before exiting the formula panel.
    2. During Row or Table creation - AddRows() is slower than DuplicateRows(). Consider the latter and then added action of ModifyRows() to blank/change values.
    3. Doc or general - Need to look at overall doc structure. Troubleshoot using Optimize calculation performance | Coda Help Center and Overview: Improve doc performance | Coda Help Center
      Also, in general, the more button columns in a table and more rows in that table will add to lag. Try to limit button columns and/or create “helper“ tables with the buttons / segregate tables of purely “data“ and tables of “functional/actions orientated“. Or consider “Archiving“ options i.e. keep only relevant data in doc.
      Lastly, more rows in a doc, will generally accumulate lag. Its got to do with coda’s performance. Which Coda have stated they’re working on We're listening: what we're up to at Coda . They’ve delivered the first two, so hopefully number 4 will be coming soon.

hope this helps!

Cheers!
Mel

1 Like