Please do this. We depend on some of the ways we rename fields to make processes clearer for our staff. And, as things move forward, we need the ability to manage how fields display and change field names in webview (assuming all functionality will eventually move from database view to webview) and have the renamed fields show up with the renamed values in system tools like query and export as well.
I wondered why some of our Opportunities fields were not being filled in by our gift officers. Come to discover, what they see as "Likelihood" in NXT, is really our repurposed "Service Line" field! Please bring these "Display As"/"Repurposed" changes from RE into NXT!
Please do this. We depend on some of the ways we rename fields to make processes clearer for our staff. And, as things move forward, we need the ability to manage how fields display and change field names in webview (assuming all functionality will eventually move from database view to webview) and have the renamed fields show up with the renamed values in system tools like query and export as well.
Please link these 4 ideas as they are essentially asking for the same thing and together they have 85 votes.
RENXT-I-222: 48 votes
RENXT-I-1814: 21 votes
RENXT-I-2523: 9 votes
RENXT-I-2548: 7 votes
Thank you.
Please link this idea to the similar/same ideas of
RENXT-I-2523
RENXT-I-2548
It's been 6 years since this was posted - any updates? This is problematic.
I wondered why some of our Opportunities fields were not being filled in by our gift officers. Come to discover, what they see as "Likelihood" in NXT, is really our repurposed "Service Line" field! Please bring these "Display As"/"Repurposed" changes from RE into NXT!
I would also like to see the above implemented.