-
Hi,
I have a field with two attributes. Is there a way to disable the changed event if the attribute changes. or is there a way to identify it is the attribute that changed.
Please help. Very Urgent.
-
I was just coming to ask a few questions and see you got it working! Hooray! :-)
-
Hi again,
Thanks so much for your help. I follow the instructions to the letter but I must be doing something wrong because at the end, the dropdown list does not display any values. My form is almost like the example in the tutorial: I have a dropdown list that displays a list of Categories (From a SP list) and then I have another dropdown ...
-
I tried without the execute but it does nothing I think its because i am using ClientContext class (Microsoft.SharePoint.Client)
I even tried this way butusing (SPSite site = new SPSite(http://sp-app))
{
using (SPWeb web = site.OpenWeb())
SPList list = ...
-
Update
I did figure out the problem I was having.
Since it is filtered, a defult value was checked. I removed the check by the value, and created a Query rule on form load that would load the data.
Dottie
-
Is this necessary?
clientContext.ExecuteQuery();
Isn't the items updated with oListItem.Update() ?
MSDN says that Update():
Updates the database with changes that are made to the list item.
-
Sure - you are going to need to use the FilterOwssvr command. Here's a PDF on using the command - let us know if you have any trouble.
-
Hi Hillary,
I have qRules. Can you please elaborate or point me to where I can find instructions on how to do it?
Thanks!!
Gus
-
Thanks for the reply, Brandon, but I don't think that will do what I hope to accomplish.
You see, the counter needs to restart at 1 for the first event of every year, and is also unique to the fields District and Division.
e.g. There can be all of the following event numbers in the list:
William Penn-North-2012-1
William ...
-
Thanks. I almost there. it works with one selection but when I select multiple items i get the following error.
SeverException was handeled by user code.
Item does not exist. It may have been deleted by another user.
Highlighted in green was clientContext.ExecuteQuery. I think it had to do with incorrect query with ...