Tag Info

Hot answers tagged

2

As Cameron pointed out, it's because of performance reason. Administrators got permission to query above the default 8 columns, standard user's do not. Microsoft states the following on their site about list performance. See the part Lookup columns and list views in the article. There's some good graphs showing what happens with the SQL performance as ...


2

You need to change the type of column colour in List#1 to LookUp. When you will select the LookUp column, you can select the List#2 in source and column colour Now your column in List#1 will be connected to List#2's colour column. Please let me know if you want further explanation. Help Link


2

you should use the itemupdating afterproperties for this: if(properties.AfterProperties["Service box"] == null) { //Cancel event properties.Cancel = true; properties.ErrorMessage = "value cannot be null"; } EDIT its todo with the current condition of the item. Your using the event itemUpdating what means that it still hasnt ...


1

I fixed it by removing the "multiple values" check! Who knew?


1

You should use this: string rawvalue = item["lookupFieldname"].ToString(); SPFieldLookupValueCollection values = new SPFieldLookupValueCollection(rawvalue); foreach(SPFieldLookupValue value in values) String.Format("{0} {1}", value.LookupValue, value.LookupId);


1

Why would you go to the categories list to see foods? Your list architecture is backwards. Foods should contain a lookup to Categories, not the other way around. Suppose you add a new food, "orange". In your scenario you have a create a list item in Foods, then go into the categories list to add the new food to the category. This is messy and error-prone. ...


1

These additional columns work exactly as if they were lookups themselves, but instead of creating them separately, you can do it in same operation. So, for example, if you create 'LookupCol1' and bring additional fields from parent list 'Title' & 'Created', these will be stored in the child list as 'LookupCol1_x003a_Title' and 'LookupCol1_x003a_Created'. ...


1

You need to create a new SPFieldLookUp http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfieldlookup.aspx and cast the context item to that object. Then you will have the SPFieldLookupValue object available to work with and you can get the value of that field in multiple contexts. Something like this should work ...


1

couple of things to check. Permission of Users on that list/library create some test alerts on that list check if it is working. Email addresses are on network or off network i.e gmail Check if Timer job for email alerts working? check this guide for detailed troubleshooting steps: http://sharepointalert.info/troubleshooting-sharepoint-alerts/ ...



Only top voted, non community-wiki answers of a minimum length are eligible