Tag Info

New answers tagged

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


2

It's the way SharePoint works, it only lets you add some specific columns(can't really remember which ones at the moment) as look-up columns, I had same issue few years ago, only solution I could find it that add a item adding event receiver and change Title column to file's name. There is no other way around I ever came across. Similar post: Lookup ...


0

I would create a new column for the lookup field, then set the Title column's value to the lookup field's value using a small workflow in SharePoint Designer.


0

The string value of a an empty lookup column is actualy "0;#". You need to test if the column is equal to this value.


0

I found a working Solution: First I decided to show the DropDowns (the simple ones - generated from the SPServices). On the page they are autofilled as they should be. Still the original Complex DropDowns were not populated with the data. Then I desided to manually select (despite already being selected) data in these Simple DropDowns. What happened was ...


1

This is a know issue with "Save Site As Template", this operation is not full fidelity Because as you said you can do it if you add the Site colum from SharePoint (from The U.I) and not from Visual Studio... Here, you can deduct that this issue is related to Visual Studio and What is happening behind the deployment Action... This Problem Has many ...


0

If you can reverse your requirement where the lookups are at a higher site than the list consuming them, then you can use site columns to accomplish this. Site columns only exist on the current site and it's subsites.


1

to my knowledge, creating a site template is not full fidelity! so that means you loose the lookup, alerts and workflows! to get around this issue you need to use: powershell: SPBackup-site http://technet.microsoft.com/en-us/library/ff607901(v=office.15).aspx or stsadm stsadm.exe -o backup ...



Top 50 recent answers are included