We have some fields where the underlying name is quite different to the display name which has led to a bit of confusion when the validation message is being shown to users that do not know what the underlying field name is. Below is an example screenshot showing what I mean:
From looking at the code this is because it is using the field’s path so doesn’t appear to be a trivial change. I then added the nested field (i.e. Array) to my example as I realised that’s probably why having the whole path is quite important, along with an example of two fields that share the same label.
This error message seems to be specifically when making use of the ‘Required on Publish’ validation, when using the ‘Required’ validation there is a less specific general message with the field specific message appearing against each field. Just mentioning in case you feel it is easier or more consistent to just use this validation messaging for all scenarios, however I do like having the validation summary mentioning specific fields, especially when you have a lot of them.
Having said all that I realise I have essentially argued against my own feature request!
Guess best bet for now is to instead push for the underlying field name to be changed to more accurately reflect the label the user sees? We’re not live yet so shouldn’t be that risky or onerous to do.