Field renaming is essential to powering your Ecosystem of Good vision. Organizations working within your ecosystem each have their own unique mission, culture, and language. Without the ability to rename fields, staff are forced to constantly translate between database labels and how they actually talk about their work—creating friction and disconnection from the platform.
For example: Our "Religion" field is actually used to track the constituent's active parish—religion isn't relevant to our mission. By renaming this field to "Active Parish," our staff feels like the system speaks our language and reflects our values. This alignment matters for adoption, efficiency, and a sense of shared purpose.
When each organization in your ecosystem can authentically express itself within RE NXT, you accomplish more together than apart. Field renaming is a small feature that has outsized impact on how well an organization can truly own their data and their story.
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!
Field renaming is essential to powering your Ecosystem of Good vision. Organizations working within your ecosystem each have their own unique mission, culture, and language. Without the ability to rename fields, staff are forced to constantly translate between database labels and how they actually talk about their work—creating friction and disconnection from the platform.
For example: Our "Religion" field is actually used to track the constituent's active parish—religion isn't relevant to our mission. By renaming this field to "Active Parish," our staff feels like the system speaks our language and reflects our values. This alignment matters for adoption, efficiency, and a sense of shared purpose.
When each organization in your ecosystem can authentically express itself within RE NXT, you accomplish more together than apart. Field renaming is a small feature that has outsized impact on how well an organization can truly own their data and their story.
Linked ideas: Updated 5/23/2025
RENXT-I-222: 94 votes
RE7-I-1814: 44 votes
RENXT-I-2523: 25 votes
RENXT-I-2548: 30 votes
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.