TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
Lock Column Name
Users should be able to "Lock" the name of a column. When you lock the name of a column, it asks you "Lock Reason". Users wanting to rename a column after its locked must first unlock it before being allowed to edit the columns name.

Jeffrey Hicks
Date Created
1/19/2018 10:03:02 AM
Date Updated
1/22/2018 4:29:22 AM
New Idea
Promoted By
Patricio BustosJeffrey Hicks
Kirill Bondar  Staff  1/19/2018 10:21:02 AM
What's the reason for locking column names? :)
Jeffrey Hicks 1/19/2018 10:49:59 AM
Integrators can simplify API development if they know the column name isn't going to change. The first mobile application we developed, we used column id instead of name ... so that our app would be resilient to column changes. Then the app broke when we made a new instance of the database and all the column ids changed. It was a big headache and didn't pay off. Now when we develop our APIs we just use column names instead of column ids. Its incredibly faster, easy and straight forward. However, if a teamdesk developer changes the name of the column; it will break the API.

Thank you for your question :)
Kirill Bondar  Staff  1/22/2018 4:29:22 AM
This problem is bugging us from time to time, we'll have a look. Perhaps we'll add an option to provide persistent API alias for objects - it will be all the way better than current f_NNNNN scheme based on IDs.
Back to Search Results