MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Date Fields not clearing

  Asked By: Vince    Date: Jun 14    Category: MOSS    Views: 1256

I'm working on a MOSS 2007 farm that's way overcustomized. The forms look
OOTB but they're actually rendered by different pages -- I can only assume
that they're intercepting events -- and for the most part things work as
expected... except date fields. When a date field contains a value, you
can't get rid of it. These are not required fields; they just can't be
cleared once they contain a value. You open an item, blank out the date
field, submit it, and you still have the same value in there as before.

The odd page had Viewstate enabled so I turned that off, but nothing

I'm about to go mud diving here, and I wondered if anyone had any control
life-cycle suggestions about why such a thing might happen. Anything to
make the search a little shorter, you know.



13 Answers Found

Answer #1    Answered By: Shari Small     Answered On: Jun 14

Perhaps it is being filled by a workflow behind the scenes?

Answer #2    Answered By: Shane Sanders     Answered On: Jun 14

How about a custom content type? Someone could have created one to alter how
dates are treated.

Answer #3    Answered By: Jonathon Palmer     Answered On: Jun 14

There is a custom content type, and its date  fields are defined as a custom
date type field. The weird part is that in List Settings, the field type is
described simply as "Date and Time".

Too many rabbit holes. Thanks for trying to help, everyone; it's probably
just one of those things where you have to be there.

Answer #4    Answered By: Christy Palmer     Answered On: Jun 14

Checked the content type; no workflows. Good idea though.

Answer #5    Answered By: Marsha Wyatt     Answered On: Jun 14

Are these doc libs or lists? I have some doc libs that are created when I
publish an InfoPath form. There is an option to allow users to update fields,
and I believe all of those fields  are read-only unless I check the option to
allow updates.

Answer #6    Answered By: Isabel Scott     Answered On: Jun 14

They're doc libs. However, the fields  *can* be updated; they just can't be
updated to a blank value. They're not required either; the form happily
submits with the blank field, but keeps the old value.

Answer #7    Answered By: Rashad Huff     Answered On: Jun 14

So it's not InfoPath forms??????????????

Answer #8    Answered By: Kaylee Kemp     Answered On: Jun 14

Nope; just regular old SharePoint forms. Altered, yet not altered. It's
all very complicated.

Answer #9    Answered By: Terence Thornton     Answered On: Jun 14

Probably altered in SPD. Would be easy to check that.

Answer #10    Answered By: Hank Ratliff     Answered On: Jun 14

I'm 99.99% sure it has nothing to do with SPD :)

These are auto-created libraries with custom content types, with custom
add/edit/view pages which look almost exactly like the standard SP item
forms. There are also scads of event receivers, WCF calls, etc. under the

It's officially assigned to someone else, so I'm not going to spin my wheels
too much until asked. Thanks for chiming in.

Answer #11    Answered By: Shawn Pennington     Answered On: Jun 14

Check to see that there isn't some weird JavaScript in the page that sets it
upon submit...maybe it's updating based on the value sitting in a hidden field?

Answer #12    Answered By: Charmaine Galloway     Answered On: Jun 14

It's worth checking... but the matching Request.Form field actually comes in
blank. Most likely there's some double-looped spaghetti in there somewhere.

Answer #13    Answered By: Rosalie Buckner     Answered On: Jun 14

I'm wondering if could you somehow disable the custom event
receiver (if it exists) on the list to see if the behavior persists when
it just uses the default save method?

Didn't find what you were looking for? Find more on Date Fields not clearing Or get search suggestion and latest updates.