locked
SPF 2010 - input field length & keeping track of changes to list values RRS feed

  • Question

  • Hello there,

    Just wanted to throw these two questions out there.

    1. I am trying to create custom forms (Create/Edit/Display) for a list and I am trying to figure out the best way to change the input value field length. By default, it looks like its about 300px wide, which just takes too much real estate on the screen. Before changing stuff I shouldn't change, I thought I could ask those who know more than me.

    2. In my list, I have to keep track of a few dates (Enrolled, Deactive, Dues Paid etc..). When these values are changed, is there a way to store the old value and make a note of which user changed the value? Basically, keep a history of changes. In the long run, I can see this extending to other information in the list as well. So, the question is, what is the best way to keep track of values that are changed (as in what was the previous value, who changed it and when)

    If any one has any thoughts, I would greatly appreciate your help.

    Thanks.
    Sri

    Thursday, March 31, 2011 1:35 AM

Answers

  • Hi Sri,
    If you create a dataview (via SPD) you can change a lot of features, like the length of a text field.

    For your second question, you could create a small workflow (again in SPD) that captures all fields in variables. When a value changes, you could write the value in a multiline textfiend (with the "append text" functionality enabled). That way, you have a "history" field.
    Regards, Marijn Somers|| SharePoint Consultant- MCTS SharePoint 2007, 2010 configuring http://www.beyond-it.be || Twitter: http://twitter.com/marijnsomers || http://marijnsomers.blogspot.com
    Thursday, March 31, 2011 7:04 AM

All replies

  • Hi Sri,
    If you create a dataview (via SPD) you can change a lot of features, like the length of a text field.

    For your second question, you could create a small workflow (again in SPD) that captures all fields in variables. When a value changes, you could write the value in a multiline textfiend (with the "append text" functionality enabled). That way, you have a "history" field.
    Regards, Marijn Somers|| SharePoint Consultant- MCTS SharePoint 2007, 2010 configuring http://www.beyond-it.be || Twitter: http://twitter.com/marijnsomers || http://marijnsomers.blogspot.com
    Thursday, March 31, 2011 7:04 AM
  • Hi Sri,

    1) you can create custom forms Create/Edit/Display and attach it to a list via SharePoint designer of through a feature.

    2) Have you looked into option of enabling vesioning for your list. you can keep track of what is changed and who has changed it.

    Hope it helps

     

    Thanks,

    Amish Trivedi


    Amish Trivedi
    Thursday, March 31, 2011 7:19 AM
  • Hi Marijn,

    Thank you for taking the time to respond and address my issue.

    What I ended up doing was creating a new create/edit/view form and then changing the CSS style on the page, which reduced the length of the text field. The only problem is that as soon as I went into Advanced Mode in SPD, it said that the page would no longer be connected with the site definition and sure enough, when I added a new field in the list, this field did not show up in my custom form.

    If the datavie is a better option and does not break any kind of dependency, I had much rather go that route.

    I did figure out the second one and have been looking into the work flows with exactly the same logic you have suggested. However, I seem to be having an issue with the steps I am creating.

    The logic I have at present is as follows:

    1. Impersonation Step
      - Create variable to store date/time value in FIELD A as String
    2. Wait for FIELD A to be changed by user
      - If it changes, change FIELD B and append it with value in variable (FIELD A)
    3. FIELD A has new value that user selected
    4. FIELD B has old date value (it's meant to keep history of all the changes made to FIELD A)

    For whatever reason, when I do this, I get a value of January 1,1900 and when I tweaked it around, it resulted in a work flow error.

    Hope this makes sense,

    Sri

    Thursday, March 31, 2011 10:41 PM
  • Thanks Amish, but Marijn's suggestions is what I was after.

    Sri

    Thursday, March 31, 2011 10:42 PM
  • Hey,
    Just a question, but are your variables of the type "date" ?
    Regards, Marijn Somers|| SharePoint Consultant- MCTS SharePoint 2007, 2010 configuring http://www.beyond-it.be || Twitter: http://twitter.com/marijnsomers || http://marijnsomers.blogspot.com
    Tuesday, April 5, 2011 7:06 AM
  • Hey,

    I have tried String as well as Date, if I am not mistaken.

    I have not had a chance to look at this issue for the last few days, but as soon as I get back to that section, I will post more details.

    The last I left it, it seemed to have been doing the trick.

    Regards,

    Sri

    Tuesday, April 5, 2011 10:38 PM