Tag Info

New answers tagged

0

I solved the issue by setting the retention policy on the event's calendar to delete item the day after the event. This leaves the custom tasks assigned to the event 'orphaned,' as it removes the data from the event lookup column. I suppose I'll setup a retention policy for these items as well.


0

Only this types can be displayed as additional fields: Single line of text Number Date Date and Time Calculeted single line of text External data: OnHandQuantity More info here


0

I just came across this discussion and it has solved my issue. My data set was far smaller. It was annoyingly just over the 2,000 item at ~2,400 items. The options were to increase the list item limit which affects all lists so is not acceptable or try this solution. This article was EXACTLY what I was looking for so I am reposting it to increase it's ...


1

If you don't already have anything that is linked to that list as a lookup, you can do that manual switch. HOWEVER, be aware, that anything you already had linked into that list will change if you delete your data and reimport with the sorted values. You risk doing more harm than good that way. You're better off finding a solution that will allow for ...


0

I had a similar problem with active/inactive lookup field (for ex. employees). I added another field to lookup list (named active) and then use jquery to delete any inactive employees. In your case, the extra field would be the field that you filter. If this approach suits you, comment me to write also the code (jquery + Ajax).


0

I wasn't able to accomplish this with one list, but I created a workflow to create an item in a new (placeholder) list with the column that I wanted. From there I use the lookup on this placeholder list. The permissions on the main list stay intact and I'm able to use the one column as a lookup still (via another list).


0

This error can occur if you are not requesting the field in your CAML Query. For example: var query = new SPQuery { ViewAttributes = "Scope=\"RecursiveAll\"", RowLimit = 100, ViewFields = ...


0

Something similar happened to me a while ago, and the solution was to modify the XSLT using SharePoint Designer: Look for the tags that should look like this: <xsl:value-of disable-output-escaping="yes" select="@Applications"/> <xsl:value-of disable-output-escaping="yes" select="@Project_Type"/> I'm assuming that your columns are called ...


0

When you edit the site column, there is a choice to "Update Lists" which should propagate the change to all lists using that column (at the cost of removing any customizations made in those lists). If you are making the change programmatically rather than through the SharePoint UI, the Update method takes a Boolean to specify if you want to push the change ...


0

How about this as a solution, Say the choice column that you want to use is called 'My Choice', create a calculated column with the formula [My Choice] then this calculated column is available in the "Add columns to show additional fields" options. This will probably also do for a look-up column too. It seems to work for me but I'm sure Microsoft will ...


0

Rather than use folders, I create views of the document library and filter the files to display them for your various usergroups. Then, I create a SharePoint "links list" to manage access to these document library views. For example: My flat library contains files for two usergroups. I create two views: Usergroup01.aspx and Usergroup02.aspx. ...



Top 50 recent answers are included