This post has been closed as a duplicate. All votes have been moved to the original: Have separate Field API Names vs Label
We present client-specific forms in Workfront. There will be times when two clients will each need a field called X but with different, client-specific properties. For example, each of our clients manages multiple brands. We want to create a drop-down field of Client A’s brands, and a drop-down field of Client B’s brands. Both clients need to see their field called “Brand” on their forms, but today, two different drop-downs cannot both have a Label of “Brand”. We are forced to invent a label the client doesn’t recognize. This is a problem which will compound as we bring more and more clients on board.
The request is to allow multiple fields to be labeled the same but have a different unique ID to differentiate them so they can have different attributes and be used for different purposes/clients.