Considerations

The Field Label is the name that appears for a field in an open record. And, through the magic of Field Management, you can change the label so that it is called something else in that open record. 

If you have the Catholic version of the Platform, we've updated some Field Labels throughout the system so you can do YOUR church YOUR way.

But regardless of which version of the Platform you have, you have the power to change Field Labels. This may seem like a really great, super fun, and very exciting feature, but you should exercise that power with extreme caution.

• Changing a Field Label changes how it appears in an open record. It will not change how it appears anywhere else in the Platform. Want to take this customization to the next level? Start working through the Label Customization checklist for a seamless User experience.
• Changing a Field Label is record-dependent. That means that you'll need to change the Field Label every single time it appears in an open record. So if you wanted to change the "Nickname" field to "Goes By," you'd need to add a Field Management record for every single time "Nickname" appears in an open record. And we're guessing nobody has time for that.
• In addition to changing the Field Label for every page, you'll also need to change it for every sub-page. Again, depending on the field you decide to re-label, this could be incredibly time-consuming.

Consequences

In addition to the considerations above, changing a Field Label has consequences. Some are good, like having the field appear exactly how you want it. And some are not so good, like ...

• Default field lists cannot be changed, so default Page Views will show the old Field Label if it is a column header or you'll need to edit the default Page Views and alias the column headers.
• Other Platform applications do not honor Field Label changes, so the original field name will show up in ...
  • Reports
  • LifeApps
  • Widgets
  • Check-in Suite
• Relabeling fields in the Platform allows you to enjoy a custom experience, but nothing else will match your system, including ...
  • This KnowledgeBase, including instructions and screenshots
  • Learning Activities
  • Webinars
• It will become more difficult for Support to help resolve any issues you might have because your system won't match theirs.
• It might prove to be confusing to your more casual Users because what they see in an open record won't match other things they see.

While none of these consequences are a reason to not change Field Labels, we strongly recommend exercising extreme caution when making this strategic decision. And if you change your mind after changing some Field Labels, simply delete the relevant Field Management record and everything will return to it's original, as-deployed names.

Changing a Field Label

If you've carefully considered all the implications of changing a Field Label and decided you're willing to live with the consequences (both intended and unintended), here's how to proceed with caution and change a Field Label. Note: You'll need edit rights to System Setup > Field Management to change a Field Label.

1. System Setup > Field Management
2. Tap the + to create a new record
3. Add the necessary information
   • Page: The page associated with the Field Label you'd like to change.
   • Field Name: The field you're going to change. This is the Field Name that came with your Platform installation. It is not the new name you're giving the field.
   • Group Name: The "box" the field should appear in (for example, the General box above). If null, the field will appear in the General box. 
   • View Order: The order fields appear in within their Group.
   • Required: Select "Yes" to make this field required. Default is "No." 
   • Default Value: Enter the default value that works for your church. 
   • Filter Clause: Leave blank or add a condition if you're filtering a dropdown list.
   • Field Label: The Name that will appear for this field in an open record. Note: Field Management is field-specific. So if you want to change a field label that appears on more than one page and/or subpage, you'll need to create a new Field Management rule for every time that field appears in the Platform.
4. Save
5. Repeat as necessary to update every instance of the Field Label in the Platform