There are many instances like this, especially in the aforementioned XML file thanks to the way that Specify 6 was developed.
As we push localization and multi-language support going forward, hard-coding these things eliminates our ability to use the schema names for these fields, which are already valid. There is no need to hard-code labels in these instances.
As reported by @bronwyncombs, the field
value
on the pick list item form has the label "value" (with a lowercasev
) on every database.This is because this was hard-coded into the XML:
Source: system.views.xml
Same story for the
PrepType
form:and for the
PickList
form:There are many instances like this, especially in the aforementioned XML file thanks to the way that Specify 6 was developed.
As we push localization and multi-language support going forward, hard-coding these things eliminates our ability to use the schema names for these fields, which are already valid. There is no need to hard-code labels in these instances.