Tag Info

New answers tagged

0

The issue in this case was a version mismatch between the referenced Microsoft.SharePoint.Client.dll and the SharePoint Server version. The DLL file was the RTM version (15.0.4420.x) while the server was on Service Pack 1 (15.0.4569.1000). After updating the reference, it worked as expected.


0

Try like this: userprofile["propertyname"].Add(" "); userprofile["propertyname"].AddTaxonomyTerm(taxonomyterm); userprofile.Commit();


0

Update: I couldn't find any built-in functionality. I came up with a helper class. It is working very well so far. As far as my tests go I couldn't find any issues regarding localization or anything else. namespace MyCompany.Common.SharePoint.Ecm.Taxonomy { using System; using System.Collections.Generic; // See ...


1

Just found a link for this.. A possible workaround. Relevant part: Create calculated column with formula comparing the two fields, final value as boolean Use this column in caml query like any other boolean (yes/no) column


0

I think you should using LINQ. var a= from c in olist.Items.OfType<SPListItem>() Where convert.ToString("ColumnName1") != convert.ToString("ColumnName2") select c; Ref


0

The query is not properly formatted. You should specify the lookup ID of the term that you want to match. like: <FieldRef LookupId="TRUE" Name="ItemType" /> Here is a sample example showing how to work with metadata columns: <Query><Where><In><FieldRef LookupId="TRUE" Name="ItemType" /><Values><Value ...



Top 50 recent answers are included