TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
Column Form Properties integrated with Column Properties
Just wondering if column form properties could be included in the standard column property setup..
One more section to include, at column property level:
Label Above Alternative Label Width Same Row

Quite often, this is done as a two part process, but could have been done as a single process

Date Created
5/21/2018 2:45:11 AM
Date Updated
5/30/2018 12:15:28 AM
New Idea
Promoted By
Dale OliverPhilipp Matuschka (MMB)Patricio Bustos
Philipp Matuschka (MMB) 5/30/2018 12:15:28 AM
If this is being worked on then I would also like to see the ability to give columns an alternative name for use in lists in views. I think when the new form editor was introduced a few years ago the use of the reference columns versus the proxy column was implemented slightly wrong and this would be an opportunity to fix it.

Example: I have a lookup from Table Contacts to Table Addresses. In Contacts the column is called Address and the proxy is called Address name.

So when I create a form containing the column Address, then it View mode it displays the label Address and the content of the proxy field Address name. That is good.

However in a List or View it shows the label Address name and the content of Address name, which looks a bit silly. It should be showing the label address.

I see a few possible solutions to this

i) in the form use the label from the proxy column instead of the reference column. For me, this is what should have been done in the first place but probably too late as this would mean everyone would have to go back and change all their forms and/or column names

ii) when creating a view and including columns which are reference columns allow the option to tick a box which says that you actually want the content of the proxy column to be displayed. Fiddly and I can see problems should you ever want both columns in the view.

iii) the reverse of ii) i,e when including columns in views which are the result of a lookup, being able to tick a box which says use the label from the reference column instead.

iv) as suggested above, when creating a column, have an alternative label for use in Views. So in above example the column Address name would have the alternative label Address
Back to Search Results