episerver - Issue with Newly Added Property Not Visible in Edit Mode in CMS 12 - Stack Overflow

admin管理员组

文章数量:1388911

We are encountering an issue in CMS 12 where newly added properties are not visible in edit mode. Upon investigation, we noticed that the property is missing in the query being fired, indicating that it's not syncing with the database correctly.

Interestingly, the same properties are visible on the local database and in edit mode, but they do not appear on the deployed environment. Below is the db query for local db that has these 2 newly added properties & the property is visible in Edit Mode Local environment.

We do have the below settings in my appsettings.json

{ "EpiServer": { "Cms": { "DataAccess": { "UpdateDatabaseSchema": "true" } } }

Here's the error logs from DXP

Here's the property i have added on Startup page:

        [Display(GroupName = Global.GroupNames.SiteSettings, Name = "Optimizely Form Uploaded Files Folder Id", Description = "Folder Id associated with the Optimizely Form File Upload element for storing uploaded files.", Order = 170)]
        [CultureSpecific]
        public virtual string OptimizelyFormUploadedFilesFolderId { get; set; }

        [Display(GroupName = Global.GroupNames.SiteSettings, Name = "Dummy Property", Description = "Dummy Property.", Order = 180)]
        [CultureSpecific]
        public virtual string DummyProperty { get; set; }

Has anyone else experienced this issue or can offer any guidance on how to resolve it? Any insights would be greatly appreciated!

We are encountering an issue in CMS 12 where newly added properties are not visible in edit mode. Upon investigation, we noticed that the property is missing in the query being fired, indicating that it's not syncing with the database correctly.

Interestingly, the same properties are visible on the local database and in edit mode, but they do not appear on the deployed environment. Below is the db query for local db that has these 2 newly added properties & the property is visible in Edit Mode Local environment.

We do have the below settings in my appsettings.json

{ "EpiServer": { "Cms": { "DataAccess": { "UpdateDatabaseSchema": "true" } } }

Here's the error logs from DXP

Here's the property i have added on Startup page:

        [Display(GroupName = Global.GroupNames.SiteSettings, Name = "Optimizely Form Uploaded Files Folder Id", Description = "Folder Id associated with the Optimizely Form File Upload element for storing uploaded files.", Order = 170)]
        [CultureSpecific]
        public virtual string OptimizelyFormUploadedFilesFolderId { get; set; }

        [Display(GroupName = Global.GroupNames.SiteSettings, Name = "Dummy Property", Description = "Dummy Property.", Order = 180)]
        [CultureSpecific]
        public virtual string DummyProperty { get; set; }

Has anyone else experienced this issue or can offer any guidance on how to resolve it? Any insights would be greatly appreciated!

• episerver
• optimizely

Share Improve this question Follow edited Mar 20 at 17:04 Farhin Shaikh asked Mar 15 at 16:34 Farhin ShaikhFarhin Shaikh 24511 silver badge1010 bronze badges 3

• Anything in the logs? On startup, you should be able to see if there are any schema update issues. – Ted Nyberg Commented Mar 20 at 8:57
• i get null exception error as 2025-03-20T16:26:08.751414270Z System.NullReferenceException: Object reference not set to an instance of an object. 2025-03-20T16:26:08.751418287Z at *****.EpiServer.Models.Pages.StartPage_DynamicProxy.get_OptimizelyFormUploadedFilesFolderId() I added the log screen shot in my question. i m not sure why i get that since it's a newly added property & is not even a required field – Farhin Shaikh Commented Mar 20 at 17:02
• i tried adding another dummy property but even that doesn't show up on the deployed version – Farhin Shaikh Commented Mar 20 at 17:08

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

The `UpdateDatabaseSchema` will only affect database schema updates when changing Optimizely version.

This problem typically occur when someone have added or changed things in the CMS Admin gui for content types and can be handled by resetting the content type in the Settings > Content Types section.

Note, this will remove any local changes in the Content Type, but typically if you are deploying content types there should not be any tampering in the admin gui anyway.

Images seems broken at the moment, see this link https://i.imgur/WyXEza5.png

本文标签： episerverIssue with Newly Added Property Not Visible in Edit Mode in CMS 12Stack Overflow