Disable alerts when using button() formula

[Breno_Nunes]

Is there a way to set alerts to “only for errors” when using button() formula or disable them completely?

[Saul_Garcia]

Hello @Breno_Nunes!
You can set the alertType parameter to Errors or None

alertType="Errors"
or
alertType="None"

I made a table template to generate buttons easily

[Breno_Nunes]

Awesome!.
Thank you

[Christiaan_Huizer]

hi @Breno_Nunes , just out of curiosity, why would you use this function if you can have a real (and stable) button at your disposal?
cheers, Christiaan

[Breno_Nunes]

Hi, @Christiaan_Huizer.
I use button() formula mostly to concatenate buttons. You get much more concise tables and better user experience.
I created a mock table to demonstrate my use case.

[Christiaan_Huizer]

that is interesting @Breno_Nunes , merci for sharing. This gives some inspiration!
about a year ago I tested this function, but at that time it was not stable (docs crashed), I guess this is no longer the case, right?

[Paul_Danyliuk]

Button()s won’t crash docs anymore — invalid parameters (invalid color, icon etc) will simply be ignored now.

[Breno_Nunes]

I just updated the mock doc with another use case.
All of that I took from @Paul_Danyliuk posts and showcase

[Nad]

I have been using Coda since it was in beta, and it’s only now and thanks to this thread that I understood the usefulness and power of the button() formula! buzzing with ideas on how to improve the interface of many of my docs now!

@Saul_Garcia: Your template looks very handy, but it opens in view only cannot be copied. How can I go about using it ?

[Nad]

As a follow-up: Is there a way to formulaically check whether a given button (in a ‘button’ type column) is disabled ?
A nice addition when ‘concatenating buttons’ in a table would be to skip the ones that are disabled - how awesome would that be!

Of course I could take out the ‘disable if’ formula of the button into its dedicated column and reference that, but that would result is a lot of additional intermediate columns, one for each button that I want to concatenate.

PS: anyone knows what the ‘actionBuilderOptions’ parameter of button() does? any useful tricks we could get out of it?

[Saul_Garcia]

Hello @Nad! Yes, I had the same reaction when I started using the button() formula! such a game changer! I scoured the community for info on how to use them and decided to make a template out of it.
I added a button to copy the doc

@Nad

As a follow-up: Is there a way to formulaically check whether a given button (in a ‘button’ type column) is disabled ?

Regarding to this, it doesn’t seem to be a straight forward way of doing it (apart from creating a checkbox column with a formula).
But! a Dark Wizard already found a way

How can I ask via formula if a button is active or not?

As @Kristofer_Tripp said, the best approach would be to calculate if the button should be enabled/disabled as a separate column, then both filter by that value and use that value in “Disable if” formula of a button, inverted. However, for answer completeness — yes, you can filter out the buttons that are disabled, i.e. whose action is internally set to _Noop(), with a formula like this: Find('"name":"_Noop"', _Merge(thisRow.[My button]) + "") = -1 [image] Warning: this is a discouraged appr…

[Nad]

The Dark Wizard strikes again!
Thanks for the finding Paul’s post which I somehow missed. Indeed, parsing the internal representation just to determine whether the button is disabled seems a little bit overkill for my use case.