none
List not saving data

    Question

  • Hi

    Aaagh - Sharepoint can be sooo frustrating at times! We have a new document library that has a number of documents already uploaded to it. Yesterday I added a new existing field - Category - and a colleague started to modify the details for all the documents - ie apply a category to each of them - so that the default view could be grouped according to this column. However after completing a number of them there are about a dozen that, try as we might, will not allow him or I to apply a category. All we're doing is choosing to edit the item and placing some text in the Category box and then saving the item. No error is thrown but the list refuses to update accordingly with the item category still remaining empty. I have even tried deleting items and recreating them.

    Has anyone else had this problem and more importantly has anyone found a fix to it?

    Thanks
    Thursday, October 08, 2009 8:42 AM

Answers

  • Hi,

           Try changing the  field - Category settings to contain information ( mandatory field) and try updating itz  value.

        You have added it from an Existing column  from sharepoint site columns.........

         So you won't be able to do what mentioned above.

         You should try creating a  custom column with the name 'Category' in the document library.

         You won't be able to create one directly as it will say that column with the name already exists. in that  case go to site actions- site settings- site columns- locate 'Category' and rename it to Category1.

        I  tried recreating the issue and it works fine with proper updation of the category column. may be some settings mat have made in the site columns at your end which restrict the updation.

    Regards, Aj (http://www.ajittgeorge.blogspot.com) MCTS
    • Marked as answer by sjb500 Thursday, October 08, 2009 10:43 AM
    Thursday, October 08, 2009 10:29 AM

All replies

  • The only thing I can think of is that you have specified Category as a Choice type and in the definition included the fact that only texts from the Choice list can be selected.

    In that case you would when amending items separately not have the addition box that allows you to add different values (so you wouldn't get your problem), but maybe you are trying to do this in Datasheet View ?


    (Note that the Choice field would be the usual kind of field for a category field that you want to use in Views).

    WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com
    Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx
    • Edited by Mike Walsh FIN Thursday, October 08, 2009 8:57 AM final note added
    Thursday, October 08, 2009 8:55 AM
  • Thanks. In this case Category is not a choice type - it's just a straight forward text box - no drop-down. As for the editing, I'm not doing it in the datasheet view (although I've tried) - I'm doing the editing from the edit properties link on clicking the little arrow alongside the item.
    Thursday, October 08, 2009 8:58 AM
  • Hi,

           Try changing the  field - Category settings to contain information ( mandatory field) and try updating itz  value.
    Regards, Aj (http://www.ajittgeorge.blogspot.com) MCTS
    Thursday, October 08, 2009 10:02 AM
  • Sure - um, how do I make it mandatory? I've clicked on the column in question on the listedit.aspx page but it doesn't appear to let me set it as required.
    Thursday, October 08, 2009 10:11 AM
  • Hi,

           Try changing the  field - Category settings to contain information ( mandatory field) and try updating itz  value.

        You have added it from an Existing column  from sharepoint site columns.........

         So you won't be able to do what mentioned above.

         You should try creating a  custom column with the name 'Category' in the document library.

         You won't be able to create one directly as it will say that column with the name already exists. in that  case go to site actions- site settings- site columns- locate 'Category' and rename it to Category1.

        I  tried recreating the issue and it works fine with proper updation of the category column. may be some settings mat have made in the site columns at your end which restrict the updation.

    Regards, Aj (http://www.ajittgeorge.blogspot.com) MCTS
    • Marked as answer by sjb500 Thursday, October 08, 2009 10:43 AM
    Thursday, October 08, 2009 10:29 AM
  • Brilliant, thanks - that's worked. What I did was rename the existing column to CategoryOld. Create a new one as you suggested (although not set as mandatory). Then use the Datasheet view to quickly complete the information in this new column. Finally I deleted the old column and changed the default views group by criteria.

    That said, I must say these all too frequent Sharepoint 'features' are more than slightly irritating - constantly makes me nervous about using it for any mission critical stuff. Microsoft, take note!
    Thursday, October 08, 2009 10:42 AM
  • I'd still suggest repeating this (new field; copying via datasheet view to new field; deleting old field) only using the Choice type of field.

    What you will find if you don't present a list of optional texts to your users is that you will have an ever-increasing number of different texts / different spellings and thus your Grouping won't be as usual as it should be

    WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com
    Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx
    Thursday, October 08, 2009 11:09 AM
  • Ordinarily I'd agree - but in this case, given this experience, I'm now nervous about using any existing columns (text or otherwise) as opposed to one that I have created by hand. Also I'm not the one (usually) editing this list and so I do not know beforehand what the list of different categories are and even if the editors use 'wrong' categories (ie misspell, duplicate etc) they will soon be able to see the error of their ways from the default grouped view.

    Thanks for the input though.
    Thursday, October 08, 2009 11:14 AM
  • >I'm now nervous about using any existing columns

    Your now tested method will work fine. The type of field won't affect it and this wouldn't be an existing column!

    You can have Choice + allow additions. That gives you the best of both worlds. A list of texts for them to choose from and if they don't like them the ability to add a new text. This cuts down the number of new texts considerably and gets rid of most of the new spellings. 

    (About once a month you should go through the lists of texts to see what has been added and either add them to the Choice list or convert them to something that is in the Choice list.)

    But as always it's up to you. I can just give you a suggestion based on a few years experience with the use of a field called CategoryX in Views using Grouping (see the WSS FAQ site ...) and with users in company sites.

    Mike

    WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com
    Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx
    Thursday, October 08, 2009 11:21 AM
  • Ah of course you're just refering to the data type - sorry for the misunderstanding. Either way I think I'll just continue with this 'new' free-text field...
    Thursday, October 08, 2009 12:09 PM
  • Hi Mike,

    I am also facing simillar kind of issue with one choice field in document properties.

    We did migrate from MOSS 2007 to MOSS 2010

    There are several choice fileds in the document properties,but the data is not sticking to only one choice filed

    Another strange thing is this is happneing only with Office 2010 documents. For other documents,this is working obsolutely fine.

    I can't create new column which leads to data lose as lot of documents have data in the existing field.

    Please help me out

    Thanks,Harini

    Thursday, March 29, 2012 6:40 AM