Add the ability to change the name of a field to reflect the terminology already used internally
In Database View we are able to change field names so that they fit the terminology used internally or so that an unused field can be used for something more relatable. Example is that Oxbridge use Matriculation Year instead of Class of. This would make NXT more personalised for each organisation, as terminology differs across the sector
-
Gemma Hayden
- Apr 12 2024
- Reviewed: Voting Open
Related ideas
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.
There are a few other ideas that could also be linked to this one.
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
Merge this with RENXT-I-222 (created in 2016!) with 94 votes.
We would like to customize field names for Opportunities to match the choices in database view.