Validation error: This property can not be set to a null value [updated with test case!] RSS

• • Reply
  

  andrerav

  Member

  12 Points

  18 Posts

  Validation error: This property can not be set to a null value [updated with test case!]

  Mar 05, 2009 12:26 PM|LINK

  Hi,
  
  In a dynamic data web application, I get a validation error on a non-null nvarchar(50) column in ListDetails.aspx, even though I have entered a value which should be accepted. The validation error is: "This property cannot be set to a null value.".
  
  I can not reproduce this on northwind/adventureworks.
  
  Any ideas?
  
  UPDATE: I have created a complete test case: http://printf.no/DynamicDataBugTest.zip (The archive was scanned with the latest AVG definitions before uploading to my private secure dedicated FreeBSD server)
  
  The test case contains:

  • One Dynamic Data Web App project
  • One MS SQL Server 2005 database backup which contains a single table with three columns
  • One screenshot showing how the error manifests itself

  
  
  I am fairly convinced now that this is a reproducible DD bug.
  
  -Andreas
  • Edited by andrerav on Mar 10, 2009 09:26 AM
  • Edited by andrerav on Mar 10, 2009 09:26 AM
• • Reply
  

  sjnaughton

  All-Star

  27387 Points

  5483 Posts

  MVP

  Re: Validation error: This property can not be set to a null value

  Mar 05, 2009 12:54 PM|LINK

  Can you post the schema of the table in question? And is the error shown as a DD Validation error or a Yellow screnn?

  Dynamic Data Validation Error

  See my blog C# Bits | Twitter @sjnaughton
  Always seeking an elegant solution.
• • Reply
  

  andrerav

  Member

  12 Points

  18 Posts

  Re: Validation error: This property can not be set to a null value

  Mar 05, 2009 01:01 PM|LINK

  It's a DD validation error message. Red, scary text :) I need to correct my initial post though -- the problematic columns are indeed nullable! Here's the basic schema:

  CREATE TABLE [dbo].[Member](
  	[Id] [int] IDENTITY(1,1) NOT NULL,
  	[RoleId] [int] NOT NULL,
  	[CommitteeId] [int] NOT NULL,
  	[ViceForId] [int] NULL,
  	[FirstName] [nvarchar](50) NOT NULL,
  	[LastName] [nvarchar](50) NOT NULL,
  	[Title] [nvarchar](50) NULL,
  	[StreetAddress] [nvarchar](50) NULL,
  	[PostalNumber] [nvarchar](20) NULL,
  	[PostalAddress] [nvarchar](50) NULL,
  	[WorkPhone] [nvarchar](20) NULL,
  	[WorkMobile] [nvarchar](20) NULL,
  	[HomePhone] [nvarchar](20) NULL,
  	[HomeMobile] [nvarchar](20) NULL,
  	[Email] [nvarchar](255) NULL,
  	[StartDate] [datetime] NULL,
  	[EndDate] [datetime] NULL,
  

  I also do a model update + recompile whenever I make changes to my database.
• • Reply
  

  andrerav

  Member

  12 Points

  18 Posts

  Re: Validation error: This property can not be set to a null value

  Mar 05, 2009 01:05 PM|LINK

  Another relevant tidbit is that this only happens in rows when the current value is an empty string (example: StreetAddress). For any row where the string is non-empty, it works fine.
• • Reply
  

  sjnaughton

  All-Star

  27387 Points

  5483 Posts

  MVP

  Re: Validation error: This property can not be set to a null value

  Mar 05, 2009 01:36 PM|LINK

  Is it the StreetAddress that is the column or is it any column that causes the error?

  Dynamic Data Validation Error

  See my blog C# Bits | Twitter @sjnaughton
  Always seeking an elegant solution.
• • Reply
  

  sjnaughton

  All-Star

  27387 Points

  5483 Posts

  MVP

  Re: Validation error: This property can not be set to a null value

  Mar 05, 2009 01:50 PM|LINK

  andrerav

  CREATE TABLE [dbo].[Member]( [Id] [int] IDENTITY(1,1) NOT NULL, [RoleId] [int] NOT NULL, [CommitteeId] [int] NOT NULL, [ViceForId] [int] NULL, [FirstName] [nvarchar](50) NOT NULL, [LastName] [nvarchar](50) NOT NULL, [Title] [nvarchar](50) NULL, [StreetAddress] [nvarchar](50) NULL, [PostalNumber] [nvarchar](20) NULL, [PostalAddress] [nvarchar](50) NULL, [WorkPhone] [nvarchar](20) NULL, [WorkMobile] [nvarchar](20) NULL, [HomePhone] [nvarchar](20) NULL, [HomeMobile] [nvarchar](20) NULL, [nvarchar](255) NULL, [StartDate] [datetime] NULL, [EndDate] [datetime] NULL,

  Is this from right clicking the table and going:

  

  If not could you do that and paste as I can't see a PK or any constraints. [:D]

  Dynamic Data Validation Error

  See my blog C# Bits | Twitter @sjnaughton
  Always seeking an elegant solution.
• • Reply
  

  andrerav

  Member

  12 Points

  18 Posts

  Re: Validation error: This property can not be set to a null value

  Mar 05, 2009 02:06 PM|LINK

  The error can happen for any of the nullable nvarchar columns if the corresponding value in a row is an empty string. Here's the complete script:

  /****** Object:  Table [dbo].[Member]    Script Date: 03/05/2009 16:05:51 ******/
  SET ANSI_NULLS ON
  GO
  SET QUOTED_IDENTIFIER ON
  GO
  CREATE TABLE [dbo].[Member](
  	[Id] [int] IDENTITY(1,1) NOT NULL,
  	[RoleId] [int] NOT NULL,
  	[CommitteeId] [int] NOT NULL,
  	[ViceForId] [int] NULL,
  	[FirstName] [nvarchar](50) NOT NULL,
  	[LastName] [nvarchar](50) NOT NULL,
  	[Title] [nvarchar](50) NULL,
  	[StreetAddress] [nvarchar](50) NULL,
  	[PostalNumber] [nvarchar](20) NULL,
  	[PostalAddress] [nvarchar](50) NULL,
  	[WorkPhone] [nvarchar](20) NULL,
  	[WorkMobile] [nvarchar](20) NULL,
  	[HomePhone] [nvarchar](20) NULL,
  	[HomeMobile] [nvarchar](20) NULL,
  	[Email] [nvarchar](255) NULL,
  	[StartDate] [datetime] NULL,
  	[EndDate] [datetime] NULL,
   CONSTRAINT [PK_Member] PRIMARY KEY CLUSTERED 
  (
  	[Id] ASC
  )WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
  ) ON [PRIMARY]
  
  GO
  ALTER TABLE [dbo].[Member]  WITH CHECK ADD  CONSTRAINT [FK_Member_Committee] FOREIGN KEY([CommitteeId])
  REFERENCES [dbo].[Committee] ([Id])
  GO
  ALTER TABLE [dbo].[Member] CHECK CONSTRAINT [FK_Member_Committee]
  GO
  ALTER TABLE [dbo].[Member]  WITH NOCHECK ADD  CONSTRAINT [FK_Member_Member_Vice] FOREIGN KEY([ViceForId])
  REFERENCES [dbo].[Member] ([Id])
  GO
  ALTER TABLE [dbo].[Member] NOCHECK CONSTRAINT [FK_Member_Member_Vice]
  GO
  ALTER TABLE [dbo].[Member]  WITH CHECK ADD  CONSTRAINT [FK_Member_Role] FOREIGN KEY([RoleId])
  REFERENCES [dbo].[Role] ([Id])
  GO
  ALTER TABLE [dbo].[Member] CHECK CONSTRAINT [FK_Member_Role]
  

  • Edited by andrerav on Mar 05, 2009 02:08 PM
• • Reply
  

  ricka6

  All-Star

  15088 Points

  2277 Posts

  Microsoft

  Moderator

  Re: Validation error: This property can not be set to a null value

  Mar 06, 2009 04:47 PM|LINK

  >>I can not reproduce this on northwind/adventureworks.

  1. <div mce_keep="true">Create a new Dynamic Data project and import just one table so you can reproduce the error.</div>
  2. <div mce_keep="true">Create a new Dynamic Data project and import just one table from NW or AdventureWorksLT that has the same data type. You might need to change a type so they match exactly. If you can repro with NW/LT, problem solved.</div>
  3. <div mce_keep="true">Reduce complexity of your app</div>
  4. <div mce_keep="true">Add complexity of NW app</div>

  Repeat steps 3&4 until they converge, ie, you either find the bug or reproduce with NW. Report back your findings.

  Rick -ASP.Net UE @RickAndMSFT Rick on MVC, WebAPI and Azure  
• • Reply
  

  andrerav

  Member

  12 Points

  18 Posts

  Re: Validation error: This property can not be set to a null value

  Mar 10, 2009 09:23 AM|LINK

  No luck so far.
  
  However, I have created a complete test case: http://printf.no/DynamicDataBugTest.zip (The archive was scanned with the latest AVG definitions before uploading to my private secure dedicated FreeBSD server)
  
  The test case contains:

  • One Dynamic Data Web App project
  • One MS SQL Server 2005 database backup which contains a single table with three columns
  • One screenshot showing how the error manifests itself

  
  
  I am fairly convinced now that this is a reproducible DD bug.
  
  -Andreas
  • Edited by andrerav on Mar 10, 2009 09:24 AM
  • Edited by andrerav on Mar 10, 2009 09:24 AM
  • Edited by andrerav on Mar 10, 2009 09:24 AM
• • Reply
  

  sjnaughton

  All-Star

  27387 Points

  5483 Posts

  MVP

  Re: Validation error: This property can not be set to a null value

  Mar 10, 2009 10:10 AM|LINK

  Hi Andreas, I found what was wrong initially I got the same error on my system as yours but I noticed that even when I made a change to the Global.asax.cs file this was not relected in the running website so I deleted the contents of the bin and obj folders (usually hidden just click the "Show All Files" button) recompiled and all was fine the error was gone. All I can think of it's some setting on your copy of VS not recompiling the website because once I had deleted the comipled files I can make changes and rerun and the changes now are there straight away.

   

  Hope this helps [:D]

  Dynamic Data

  See my blog C# Bits | Twitter @sjnaughton
  Always seeking an elegant solution.
  • Marked as answer by ricka6 on Mar 11, 2009 02:14 AM