Error on Forms for editors Submit

Shiwanka Chathuranga

Posted on 25/02/2025 05:58:59

Latest DW 10.12.4 error on Forms for editors submit function

An error occurred while attaching module (Dynamicweb.Frontend.Content)

System.ArgumentException: Column 'FormSubmitId' does not belong to table Table.
at System.Data.DataRow.GetDataColumn(String columnName)
at System.Data.DataRow.set_Item(String columnName, Object value)
at Dynamicweb.Forms.Internal.SubmitRepository.MapToDataRow(DataRow dataRow, Submit model)
at Dynamicweb.Forms.Internal.SubmitRepository.Upsert(Submit submit)
at Dynamicweb.Forms.Internal.DefaultSubmitService.Save(Submit submit)
at Dynamicweb.Forms.Frontend.SaveForm()
at Dynamicweb.Forms.Frontend.GetModuleContent()
at Dynamicweb.Frontend.Content.GetModuleOutput(Paragraph paragraph, PageView pageview)

Replies

Nicolai Pedersen

Posted on 25/02/2025 17:36:08

You must have done something to the DB.

It is a standard table and field and has always been there. Below the script that creates the table on db install. Pls check if you are missing the table.

SET ANSI_NULLS ON

SET QUOTED_IDENTIFIER ON

CREATE TABLE [dbo].[FormSubmit](

[FormSubmitID] [int] IDENTITY(1,1) NOT NULL,

[FormSubmitFormID] [int] NULL,

[FormSubmitDate] [datetime] NULL,

[FormSubmitIp] [nvarchar](30) NULL,

[FormSubmitSessionId] [nvarchar](30) NULL,

[FormSubmitPageId] [int] NULL,

[FormSubmitUserId] [int] NULL,

CONSTRAINT [DW_PK_FormSubmit] PRIMARY KEY CLUSTERED

(

[FormSubmitID] ASC

)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

) ON [PRIMARY]

Shiwanka Chathuranga

Posted on 25/02/2025 17:41:16

HI Nicolai

it was there already, but i see extra one column [FormSubmitReferer], but i dnt think that has anything to do with error

Nicolai Pedersen

Posted on 25/02/2025 17:49:07

Maybe you are on another database than the one you are looking in?

Shiwanka Chathuranga

Posted on 25/02/2025 17:51:05

Morten Snedker

Posted on 28/02/2025 10:27:42

Hi Shiwanka,

I can reproduce the error locally on 10.12.5 (yours is 10.12.4). However, the error is not reproduceable on 10.13.0. So either upgrade to 10.13.0, or await the release of 10.12.6, where the issue will be resolved.

/Snedker

You must be logged in to post in the forum

Developer forum