Missing custom fields from the create or edit views of a content

An existing custom field is missing from the create or edit views of a certain content type.

Jul 24, 2018
Knowledge

Title

URL Name

Missing-custom-fields-from-the-create-or-edit-views-of-a-content

Article Number

000124093

Environment

Product: Sitefinity Version: 8.x, 9.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x OS: All supported OS versions Database: All supported Microsoft SQL Server versions

Question/Problem Description

An existing custom field is missing from the create or edit views of a certain content type.
Custom fields section not showing in title and properties while editing page.

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

There is a missing field in the view definitions for the concrete item. In order to verify this, go to Administration > Settings > Advanced > ContentView > Controls > { Content name } > Views > { View name } > Sections > { Section name } > Fields and check whether the field is amongst the other fields.

Resolution

There are two ways to resolve this:

I. Recreate the missing custom field by doing the following steps:
1. Create a new custom field for that content type that is from the same type as the missing one
2. Go to Administration > Settings > Advanced > ContentView > Controls > { Content name } > Views > { View name } > Sections > { Section name } > Fields where the new custom field is present
3. Create a new field in that section using the settings from the newly created custom field and only changing the distinctive settings (e.g. DataFieldName, Field name, etc.)
4. Remove the newly added custom field

II. Remove the lazy configurations
Note: The below approach would reset the default configurations for the views for that content type. Before using the below steps, create a copy of the configuration files and database

1. Edit the configuration for the concrete content:
The configuration can be found in App_Data > Sitefinity > Configuration if it is stored in the file system, or it can be found in sf_xml_config_items if it is stored in the database
For example, if a field is missing for the News content type, the aimed config will be NewsConfig.config

2. Remove the lazy configs by deleting the contentViewControls element:
Example for NewsConfig.config

<contentViewControls>
    <contentViewControl definitionName="NewsBackend" config:flags="1">
      <views>
        <config:lazy key="NewsBackendEdit" configFile="NewsConfig.contentViewControls.NewsBackend.views.NewsBackendEdit.config" />
        <config:lazy key="NewsBackendInsert" configFile="NewsConfig.contentViewControls.NewsBackend.views.NewsBackendInsert.config" />
        <config:lazy key="NewsBackendPreview" configFile="NewsConfig.contentViewControls.NewsBackend.views.NewsBackendPreview.config" />
        <config:lazy key="NewsBackendDuplicate" configFile="NewsConfig.contentViewControls.NewsBackend.views.NewsBackendDuplicate.config" />
        <config:lazy key="NewsBackendVersionPreview" configFile="NewsConfig.contentViewControls.NewsBackend.views.NewsBackendVersionPreview.config" />
      </views>
    </contentViewControl>
  </contentViewControls>

The above removes the references to the LazyConfigs.

3. Remove the lazy config files or entries in the database
Example for NewsConfig.config

NewsConfig.contentViewControls.NewsBackend.views.NewsBackendEdit.config
NewsConfig.contentViewControls.NewsBackend.views.NewsBackendInsert.config
NewsConfig.contentViewControls.NewsBackend.views.NewsBackendPreview.config
NewsConfig.contentViewControls.NewsBackend.views.NewsBackendDuplicate.config
NewsConfig.contentViewControls.NewsBackend.views.NewsBackendVersionPreview.config

4. Restart the project.

III. Check if the custom fields are explicitly removed in the configuration files of the site.
The configuration files can be either stored in App_Data/Sitefinity/Configuration folder or in the database in table [sf_xml_config_items] e.g in config file NewsConfig.contentViewControls.NewsBackend.views.NewsBackendEdit.config

<sections>
<remove name="CustomFieldsSection" />
<fields>
<remove fieldName="CustomField1" />
<remove fieldName="CustomField2" />
</fields>
</sections>
</sections>

Workaround

Notes

Progress Articles:

Keyword Phrase

Last Modified Date

5/7/2025 1:05 AM

Missing custom fields from the create or edit views of a content

Files(0)

Was this article helpful?

Was this article helpful?

Missing custom fields from the create or edit views of a content

Information

Related Articles