Tag Info

New answers tagged

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);


0

although I believe there would be benefit in sharing the whole background information in order to brainstorm non DOM manipulation, here is a possible solution to remove duplicates var usedNames = {}; $("select[name='company'] > option").each(function () { if(usedNames[this.text]) { $(this).remove(); } else { usedNames[this.text] ...


0

you can use jquery to remove duplicate value temporary while its showing to user take all the values of dropdown in an array and match the values if its present in an arrray if yes delete the particular array and again bind all the array to dropdown using jquery


0

I've just spent a full day on what seems to be the same issue. I'm a complete novice to this, but I finally figured out that since the XLV is a subview to the ListView, you can't use any columns that are not in that. I.e. you have to make a view that contains all the columns you want to use before your XSL stylesheet can use them. Furthermore, the ...


0

Place a lookup column in the list of foods to class and leave it as required. When you create foods you select the desired category and you can see which food belongs to category. You can only see if there is any food in the category citing them in the workflow. But limits the data. You can do the research on that REST is more advisable and possible to see ...


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'. ...


0

It is failing because you are deploying the lookup field before the lookup list. The relevant quote from the blog you referenced states: The trick to doing this right is understanding that the order in which the package deploys the artifacts is important. Look inside your feature designer, and I bet the element that provisions the lookup field occurs ...


0

If the List Item (objItem in this example) is populated: string s = new SPFieldLookupValue(objItem["MyField"].ToString()).LookupValue;


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/ ...


0

You have the workflow set to start on change, and something in that workflow changes that list item. This would create a loop which SharePoint does not allow. See if your logic allows you to use only "start on creation" instead. If not, you can work around this by bouncing workflows between two lists.


0

Fetch additional lookup columns values in REST lookupList -- List1 : col1, col2 List2: col3(lookupof col1) template: $select=LookupColName/LookupListcolName1,LookupColName/LookupListcolName2&$expand=LookupColName/LookupListcolName1,LookupColName/LookupListcolName2 Example $select=col3/col1,col3/col2&$expand=col3/col1,col3/col2


0

Test1 The List, whose column I will use a Lookup column say Test1 Test2 The List which will use the Test1's country column as lookup column is as follows: WorkFlow Now the workflow I have created is associated with Test2 Now check the condition I have put in the Workflow. I checked Current Item:Coountry2 contains India Now If I run the workflow ...


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


0

Or You can try this: $w=get-spweb http://site/ $f=$w.fields["field_name"] $f.schemaXml = "schema xml with another list ID" $f.update()


0

Yes. There are two things you have to take care of: The user/group will need atleast read permission to the Look-up List. The number of look-up columns in your list should ideally be less than 8. If there are more than 8, then you will again end up with issues.


1

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



Top 50 recent answers are included