Tag Info

New answers tagged

1

select above should be: substring-before(substring-after(@Lookup, '>'), '</a>')


3

Yes It shares this quality as SharePoint online also has lookup column threshold of 8. https://community.office365.com/en-us/f/148/t/11914


1

You can use: string value = (new SPFieldLookupValue(item["FieldName"] as String)).LookupValue


1

If it's posible. Here are the steps: Create a list in the root site. Create a site column (of type lookup) in the root site referencing the list created in step 1. In the sub site, in a list, create a column using the "Add from existing site columns" And ready. Learn more in this article: Create a SharePoint Lookup Column to Another Site


0

What is the solution to the get the value of lookup field var table = $('#example').DataTable({ "filter": true, "bDestroy": true, "bProcessing": true, "aaData": data.d.results, "aoColumns": [ { "mData": "ID" }, { "mData": "Title" },{ "mData": "lookupfield" },]


0

Remove the width and text-overflow:ellipsis from the CSS on the object Or overrule it with your own CSS


0

I had same problem, solution is just create a new SPFieldLookupValue and read LookupValue property. It's quite simple, but can save some time for others. public String LinkTitleCode { get { var lookupText = Get<String>("LinkTitleCode"); return new SPFieldLookupValue(lookupText).LookupValue; } }


0

Yes you can order the artifacts in a feature. Select the artifacts that are in the feature one at a time and click the < button remove the artifacts. Then add them to the feature by selecting them one at a time and clicking the > button to add them in the order you want. You can also double click them to add or remove them instead of selecting one ...


1

1- one solution is to use XPath functions to extract the simple inner text. see below sample <xsl:value-of select="substring-before( substring-after(@Service_, '&gt;') , '&lt;') "/> you can use some useful auto-complete XPath editor or more advanced editor in ribbon (see below image) 2- note the disable-output-escaping="yes" attribute ...


0

This really isn't supported, so test at your own risk. Remove or delete Categories list (used by discussions). Activate BlogContent Add Posts and BlogTools webparts Add link from discussions list to new Categories list. (for #1 and #4 I'm thinking whether to create a new temporary list and change the lookup definition in discussion list to the temp list, ...


1

If you're using SharePoint Foundation 2010, then this is a known issue where a custom list has a lookup field to another custom list that contains more than 20 items. If you set the value of the lookup field to "None," then you'll get the error. It looks like you'll need to apply an update to SharePoint to resolve the error. Here's more info: ...


0

I would recommend something like this. I know you said your not great with JavaScript, but I think this is going to be your best option. I have found from personal experience that InfoPath is easy to start with, and powerful to an extent, but you will soon find its limitations and flaws. If/when that happens you will be going back and starting fresh with ...


0

there are also some 3-rd party tools that allow you to add cross site lookup feature. I know that boostsolutions and arfulbits have such component.


0

Okay, I got it: only text and primitive types are allowed to be lookuped by standard mechanism. You should write your own "fixer" to achieve needed behaviour.



Top 50 recent answers are included