Dynamic button text
Canny AI
Merged in a post:
Allow "Off/On" Text in Button to be customized.
Tommy Martin
The "Off/On" style of button works great, but "Off" and "On" isn't always relevant in terms of the use case.
Being able to control what the "Off/On" states say in the button would be amazing.
Examples might be:
"Not Saved/Saved"
"Not Sent/Sent"
or even being able to have the "Off" state be blank, and the "On" state say something. 🙌
Does this affect operations? I suppose not, but would be a nice polished improvement to anyones setup.
Ara Bozadjian
agree, am sure this has been posted before?
We have a current use case in a Suppliers Table with a VAT (tax) Field:
YES / NO is fine but we struggle with being forced to choose a Default State as sometimes when adding the Supplier we are in a "don't know yet" state.
But yes, being able to custom name the YES/NO Field would also give us more use options specific to us.
E
Esther Chen
Yes this customization would be very useful!!!
Jon Darbyshire
Hey Tommy Martin, thanks for your feedback! I have a few more questions for you:
- What specific scenarios or use cases do you envision for customizing the "Off/On" text?
- Are there any specific words or phrases you would like to use for the "Off" and "On" states in your application?
- Would you like the ability to customize the button text for different user roles or contexts within your application?
Tommy Martin
Jon Darbyshire Hey Jon.
- Infinite scenarios where the yes/no field is used not related to "Off" and "On". Of course there are other button options, but the Off/On aesthetic is really nice, and would be nice to tailor the phrasing, [the same way we can add prefix/labels to certain fields.]
- Here are the two most globally useful in my opinion: Send/Sent & Hide/Hidden
- I'm not sure different user roles would need different labels for the field. I'd have to be given an example, as of now - I'd say no, not necessary.
Thanks!
Nate Montgomery @ SmartSuite
Merged in a post:
Ability to make Button Label Dynamic
C
Caleb Cook
I would love to be able to make the button text dynamic based on a formula, just like the URL is. I see this happening in two possible ways...
- Create a separate "Label Formula" option that allows me to dynamically generate the button Label. Only downside is any statements need to be duplicated between the button and could in theory go out of sync.
- Better option IMO would be to change the "Formula" option to accept an array value (ie [ URL, LABEL ]
- To avoid breaking current button configurations, the existing "Label" could be a fallback / default label if a label isn't specified in the formula.
So creating a dynamic button field would be like:
Default Label:
Click Me (or whatever people are already putting in button fields) When Formula is enabled for the button, it can accept a URL string (like it currently does) and use the Default Label field as the Label, OR if an Array is passed instead of the URL string with a second parameter, that second parameter replaces the label.
So a formula like:
IF( [Status] = "Complete", "https://make.com/1234" ) would show whatever is in the
Default Label
but IF( [Status] = "Complete", ["https://make.com/1234", "Completed Action"] ) would show
Completed Action
, or whatever I put in that second item in the array. This would reduce the need to add so many one-time use buttons and make them react to state changes - which would be a huge step forward!
Jon Darbyshire
Great to hear your perspective, Caleb Cook! I have a few more questions for you:
- Can you provide examples of the different states that would trigger a change in the button label?
- Are there any specific limitations or constraints you foresee with the proposed solution?
- How frequently do you anticipate the need to change the button labels?
C
Caleb Cook
Jon Darbyshire I would see it being formula-based just like the URL is currently - right now I primarily use IF statements to determine what the button links to, so I'd love to have that same ability to have a formula dynamically change the text to match.
I would see this being used for a lot of Make/N8N style triggers. Take my current example...
Field 1: Dropbox Folder Link
Field 2: Dropbox Request Link
Button 1: Create Dropbox Folder
Button 2: Create Dropbox Request
When I create a new project, I can either add an existing Dropbox link, or I can click the
Create Dropbox Folder
button which triggers a Make webhook that creates a Project folder, and updates Dropbox Folder Link
field with the new folder URL. The button formula is an IF statement that only returns the Make trigger link, if the Dropbox Folder Link field is empty (so that way I can't just keep clicking and creating duplicate folders - once a folder is created or manually added, the button is disabled because the formula returns null.)The
Create Dropbox Request
button links to another Make automation, which takes the folder from the Dropbox Folder Link
, creates a Dropbox File Request for that folder, and puts the link in the Dropbox File Request field. This second button URL has an IF statement that only returns the trigger link if the request link is empty AND the folder link has a URL in it. That way, I can't trigger a Dropbox Request with an empty folder string.Ideally, I'd love for it to just be one button instead of two with a formula similar to this:
IF
Dropbox Folder Link
is empty, return an array with Button 1's label and URL (Create Dropbox Folder)IF
Dropbox Folder Link
is not empty AND Dropbox Request Link
is empty, return an array with Button 2's label and URL (Create Dropbox Request)That way the button action and label follows the steps in the order that I want it to follow. This is just one example where I'd want the label to be dynamic - but there are plenty more. :)
Currently I can make the URL dynamic in this way but the label wouldn't change with it, so it would be confusing for the User to know which action they are taking. In the meantime we just have to use multiple single-use buttons.
Richard Åkerblad
Are you thinking fetching from other fields (like auto title) or formula similar to the url?
First option would work for me i think. You could then use formulas in another field.
Adam Johnston
Richard Åkerblad Either works, because as you mention you can map a formula field into an auto generated, record title esque field