TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
Custom Buttons
I'm just evaluating TeamDesk, and am planning to migrate a couple of databases from Microsoft Access.

TeamDesk looks OK, but i think Custom Buttons could be a little more powerful.

For example:
an ability to put a Custom Button on a Dashboard and it would then take you to a view or another Dashboard
An ability to locate a Custom Button in the top row of buttons on a View, which would take you to another view or a Dasboard

As far as I can see I can't do that at the moment. Or am I missing something?


Bob Blightman

Bob Blightman
Date Created
2/16/2021 5:30:34 AM
Date Updated
2/16/2021 12:19:06 PM
New Idea
Promoted By
PierrePatricio BustosBob Blightman
Pierre 2/16/2021 5:42:54 AM
Hello Bob

Welcome to Teamdesk !

You can easily put a button on the top of a view
- Create a button (Rules / custom button)
- Create a navigate action (Add an action to your button - 'New Navigate')

You can also put buttons in a form or in a table (create a URL or formula URL field, display it using the button option)

Kind regards,


Bob Blightman 2/16/2021 6:24:41 AM

Mila suggests you can't do what you suggest - here's her comment:

"It is not possible to insert a button with navigate action into the header of the view.

If you create a multi-record custom button, it is shown at the top of the view, but Navigate actions do not work with such a Multi-record custom button.
I suppose that Pierre forgot that a Navigate action does not work with Multi-record custom button."

So I still suggest that a button looking like a button would be very useful on a Dashboard


Pierre 2/16/2021 7:03:51 AM
Hello Bob

You are absolutely correct - thanks for the info.

Kind regards,

calvin peters 2/16/2021 8:02:17 AM
From a dashboard this can be done with a bit of very simple HTML coding using an href to the destination url and an HTML "INPUT BUTTON" be that a dashboard or a view. I've done this to build navigation "custom buttons" to navigate out and back.
The only way to limit access to them by role however is to build different individual dashboards for roles.
Bob Blightman 2/16/2021 11:03:21 AM

Thanks for that

Although I have a lot of IT experience, none at all really in HTML

I tried to build the HTML code like this:

<a href=''><button>Choose Active Volunteer</button></a>

And put it in a Section on my dashboard. It looks fine, but when I click on it, the screen flashes but doesn’t go to that page, remaining on the dashboard (and I’m sure the address is correct)

I can get by without it looking like a button, just a lot less elegant.

I’m already setting up different dashboards for different roles, so that’s not a problem



calvin peters 2/16/2021 11:28:01 AM
Try more like this.
This is a working button from one of my apps that works for this. It's dressed up a bit to incorporate the
required heading fields in the TEXT box. Also make sure the TEXT properties are set to HTML.

<h6>To drill into older data <i style="color:blue">CLICK!</i> on <i style="color:blue">View </i> beside one of the data rows in the grid below<br> then use the Menu in the underlying table and <i style="color:blue">CLICK!</i> on <i style="color:blue">Select Month to View.</i></h6><br><br>
<b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1&nbsp;</b><input style="color:white;background-color:DodgerBlue;width:190px;height:25px;FontSize:8" type="button" onclick="location.href='';" value="Choose Active Volunteer" />

Fix your "ID" in your href and it should work
All the extra coding above the button is just a simple text area for implanting directions to the user.
"nbsp" is simply the coding for a blank space infront of the button to format physical layout across the line when rendered. All the <h6> and "nbsp" stuff can be removed or changed for your specific use
The color and size are set inside the "style=" property of the <input> element.
<br> is a line break to advance to the next line. So this button is set 2 lines below the <h6> heading above it.
<i></i> is the coding for italics. The only tag between the <> that you don't need to close is the <br> line break. All other tags inside the <> brackets need to have an accompanying </> closing tag
<h6>" some text..."</h6>
<i>"some text to italicize"</i>
<b>" some text..."</b>
The only other exception in this example is the <input> tag. It is "self closing" meaning that the closing is done at the end of the input tag like this <input style="xx:yy;aa:bb" 'and some button coding stuff and then the closing tag like this' />

There is a ton more on this stuff at W3 Schools on the web. That's where I went to figure this out.

Good luck
Bob Blightman 2/16/2021 11:44:34 AM

That's really useful.

So I reduced the code to this:
<input style="color:white;background-color:DodgerBlue;width:190px;height:25px;FontSize:8" type="button" onclick="location.href='';" value="Choose Active Volunteer" />

and it looks great, but it generated an Internal Error when clicked on. This has been sent to the TeamDesk team. I'm sure the address is correct (I've substituted xxx for the real numbers above). Hopefully the team will tell me what's wrong

Thanks again

calvin peters 2/16/2021 11:54:30 AM
So I believe the URL is not properly completed to get to your endpoint.

Try simply removing the "/"

It also appears that your endpoint is supposed to be a VIEW so the "id" ought to be the final element in the URL. I don't think you need the "/"

Bob Blightman 2/16/2021 11:56:36 AM

Many thanks

calvin peters 2/16/2021 11:59:35 AM
Happy to help out sir.
Welcome to TeamDesk.
It has been a fantastic tool for us.

Enjoy the platform Bob
Bob Blightman 2/16/2021 12:19:06 PM

Im evaluating TeamDesk as a replacement for a Microsoft Access database that I developed for a local hospice (on a pro bono basis). The hospice are concerned that support for Access is being discontinued and also that they rely on me since there’s a lot of VBA code behind what I’ve done

So far I’m very impressed by TeamDesk and its very good to know it works for you


Back to Search Results