Renaming a custom field should not break a calculation

Who would benefit?

All users

What impact would it make?

Reports that work

How should it work?

Today, if you rename a custom field which is used in a calculation, the calculation errors. Yes you can amend the column name instead - but this causes confusion as the custom field is still named originally on the form.

E.g. Custom field called Additional Costs is on the Workspace form. In a list view report, Additional Costs is used in a formula to calculate Total Cost. We want to change the name of this custom field to Product Community Costs. This would break the calculated field in the report. This formula is used in lots of reports and dashboards. We could renamed via the Column name - but this will then have a different name to the custom field on the form.