Each built-in entity type has a standard set of fields organized into field sections. This set of fields and sections is called the default field presentation.
Default Behavior
The default field presentation has two key behaviors:
- Automatic translations: If users access the platform in multiple languages, field and section names in the default presentation are translated automatically.
- Automatic updates: When Yext makes changes to a built-in entity type's presentation (e.g., adding a field, renaming a section), accounts using the default field presentation receive those updates automatically.
Modifying the Default Field Presentation
Any modification to the default field presentation effectively "forks" it. Once forked, the presentation will no longer receive automatic translations or automatic updates from Yext.
This can lead to issues such as:
- Outdated names: For example, Yext renamed the "Google My Business" section to "Google Business Profile" following the rebrand. Accounts that had modified their default field presentation did not receive this update automatically and continued to see the old section name.
- Broken translations: A forked field presentation requires manually setting translations for all fields and sections in every desired language.
What Triggers a Fork/Breaking Changes
The following changes will fork the default field presentation:
- Renaming a field section
- Adding or removing fields on the entity type
- Moving fields between sections
- Re-ordering fields within a section
- Re-ordering sections within the field presentation
- Changing the Show on Entity Creation option for a field
Note: Changing whether a field is Required does not fork the default field presentation.
Translation Warning
If a change affects automatic translations, the system will display the following warning:
