BackendUtility::getProcessedValue() reads the Page TSconfig section
"TCEFORM.<table>.<field>." when resolving select item labels, but
ignores its "types.<type>." sub-section. Backend previews built on
RecordFieldPreviewProcessor therefore render the plain TCA item
label - or the raw value, if the item exists through the override
only - while the edit form renders the configured one.
FormEngine already solves this twice, both times the same way: strip
"types." from the field configuration and overlay the matching type
section on top of it, see PageTsConfigMerged and
FormEngineUtility::getTCEFORM_TSconfig(). The record type itself is
determined by BackendUtility::getTCAtypeValue(), which additionally
covers type fields pointing to a foreign schema, array type values
and sub schema validation.
Determining the type inline from the record row would be shorter,
but duplicates existing logic and resolves the wrong value for
tables whose type points to a field in a foreign schema. Using the
type section as the field configuration instead of merging it would
be simpler, but drops everything configured on field level, for
instance altLabels.
Both established patterns are reused instead: getTCAtypeValue() with
the fallback skipped, as FormEngineUtility does, so an undefined
type leaves the field configuration untouched, and
ArrayUtility::mergeRecursiveWithOverrule() after removing "types.",
as PageTsConfigMerged does.
Select item labels in backend previews now match the edit form for
type-specific TCEFORM overrides, while field level configuration
keeps applying. Functional tests cover an added item, an overridden
label on a table other than tt_content, and the field level
configuration surviving for a typed record.