Answer
This is a known framework limitation, not a configuration mistake — Dialog and Assistant view types don't support the standard custom field framework the same way regular pages do, which is a common surprise specifically when migrating customizations that relied on adding fields to this kind of view from an older application generation.