FormBuilder - There is a configuration left for already removed form field or form components with t

Chris Percival asked on November 28, 2023 09:10

I'm working on a MVC solution where we've started to use the Form Builder. Any new forms built are now being lost upon a re-deployment of the code, with the following error message:

There is a configuration left for already removed form field or form components with the following identifiers are not registered in the system: . Any change to the form configuration may result in lost data.

Before I removed the CMSDefaultUICulture setting from the MVC app, I was just seeing the resource string tag of "widget.missingmetadata" which corresponds to a different message "Widgets with the following identifiers are not registered in the system: {0}. Saving the page will result in lost data.". Either way, no value is supplied to the {0} parameter.

Any idea how I should go about tracking down the cause of this problem?

Kentico 13.0.73

Correct Answer

Chris Percival answered on November 29, 2023 17:17

The cause of this was CI where anything other than a preset list of formclass documents where just being removed. :(

0 votesVote for this answer Unmark Correct answer

Recent Answers


Chris Percival answered on November 28, 2023 12:14

Could I assume that as no identifiers were listed, that it was the first part that was true: There is a configuration left for already removed form field

What does this error mean?

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on November 28, 2023 14:54

Define what you mean by the "nny new forms built are now being lost"? Does the form throw an error or is the form totally removed from the system?

The form builder engine uses the page builder engine in the background. So you need to have widget identifiers in place. If you change those identifier names, it will cause a lot of problems if you already have forms built.

0 votesVote for this answer Mark as a Correct answer

Chris Percival answered on November 28, 2023 14:58

The form builder displays that error for forms that prior to deployment were displaying fine in the form builder. The form is still there in the database with (for example) the markup below.

Do you know under what circumstances that error is displayed, or do you know what it might mean?

    {
  "editableAreas": [
    {
      "identifier": "DefaultFormBuilderArea",
      "sections": [
        {
          "identifier": "00000000-0000-0000-0000-000000000000",
          "type": "Kentico.DefaultSection",
          "zones": [
            {
              "identifier": "21d4e2af-1992-4534-b90e-992d0f0bf032",
              "formComponents": [
                {
                  "identifier": "37aacf37-03d1-4bac-b135-10696a9e48a6"
                }
              ]
            }
          ],
          "properties": null
        }
      ]
    }
  ]
}
0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on November 28, 2023 15:01

What does your code look like when you started developing form components or form sections?

0 votesVote for this answer Mark as a Correct answer

Chris Percival answered on November 28, 2023 15:13

Sorry, could you explain further what you're asking?

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on November 28, 2023 15:19

Are you writing code for the form builder? Creating form sections? Did you modify your startup.cs file at all?

0 votesVote for this answer Mark as a Correct answer

Chris Percival answered on November 28, 2023 15:24

Yes, possibly, all of the above! This is a legacy site, and there are custom fields and sections. However none of existing forms suffer from this issue, only new forms. I also don't have a startup.cs file.

If I can just understand what the error means, I have a chance to fix it.

0 votesVote for this answer Mark as a Correct answer

Chris Percival answered on November 29, 2023 10:18

Anyone have the code and could tell me what the exact cause of this error is?

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.