Have separate Field API Names vs Label

Forum|Forum|8 years ago
April 12, 2017
15 replies
1988 views

We are looking to “decouple” front end element names from backend element names for Custom data elements in Workfront. Is that possible? For e.g. for this field on a custom form for tasks -

the backend field is called “DE:Has spend been committed for this campaign?”. This makes the backend fields very verbose, and the SQLs that use them hard to work with. (Note: this is a relatively short name ‚Äì some custom fields are complete and very lengthy sentences/questions)

Is there a facility (mapping) in workfront whereby we could have this element assume ‚Äì

1. A Front end name ‚Äì “DE:Has spend been committed for this campaign?”

2. A back end name ‚Äì de_spend_committed_flag

Show previous replies

V

VincentGo

New Participant

Correction to my earlier statement. When there are special characters in the field name, you can add slashes to help with calculation. Ex: (ex. "What would you like to do/? Select all that apply.")

V

VincentGo

New Participant

I agree. The Reports area has "Custom Column Label" functionality where you can overwrite the field name, and I think that should be spread to other parts of the application.

We also have punctuation/special characters in our field labels to make them more readable (ex. "What would you like to do? Select all that apply.") and we can't write Calculated Fields off these fields because of the punctuation.

K

KeithFa

New Participant

I'd like to see this as a general change overall.

When creating a custom field we should be able to have a 'name' and a 'display label'

D

DaveZeltser

New Participant

I agree! It is goofy to have to use all the underscores in the field name if you are going to post to it externally.

E

EricDe

New Participant