TeamDesk Knowledge Base & Support

Slava Shinderov  Staff  11/22/2012 2:54:48 AM

@Brett what's the reason of having a column with "Membership Type" name in "Membership Types" table?
From my point of view it's more logical to use "Name" instead, so you'll have reference column named as "Membership Type", don't have to rename anything on the form and "Membership Type Name" lookup column for usage in views.

basenine 11/22/2012 5:10:43 AM

@Slava...
Sorry, I disagree with you. For a user, calling it a [name] in one table and something else in another is confusing. I think that having the reference column name to show on the form that it is referenced also helps the user understand where it might be coming from. I.e. [Membership Type Reference]

[Memership Type Name] in a view is twofold: long winded and unnecessary - it is simply the [Membership Type]

Kind regards - Brett

basenine 2/11/2015 8:58:03 PM

An update to this request:

If all new Reference Columns (Which use the Table Id as the main reference) were suffixed with "Id" and the Auto created Lookup column could just be the Name column, this would save time and be more intuitive.
For example Table A --> Table B
Table B "*Id" is used as the reference in Table A. When the relation column ("*Id") is created, it generally uses [Name Column] and auto creates [Name Column Name Column] as the text readable value. If the Auto creation can create [Name Column Name Column], would it be impossible to instead create [Name Column Id] and [Name Column]?

I'm constantly changing these names as I like to use [Name Column Id] so I can easily distinguish the reference from the lookup...If TD could automate this process - Happy Days!