SharePoint Document Permissions?

I have a (what I thought is a simple task):
I would like to set permissions on my SharePoint 2013 on-premise as follows:
1. Each department has its own site (e.g Finance, HR, Admin etc)
2. I would like all Staff to be able to browse to each department site
3. The documents library should be accessible to members of the department in question
4. The files/folders in the document library should have List only access to all other
staff except if a particular file/folder has been explicitly shared with them.
Sounds simple right? Here's the problem I have:
Number 1 is done
Number 2 is done
Number 3 is done
Number 4 I have managed to do by granting View Only access to everyone and Read access to the Departmental members as needed.
I am not sure this is the best way to do it but it seems to work. Staff that are not members of the department can access the site, see the list of files but cant open them.
However.... I also have Office Web Apps and if they click the file it shows the contents of the file in Office Web Apps which is pointless if you don't want them to see the contents.
Prime example would be HR site. They have some very sensitive documents that should not be seen by non HR staff but other documents that they wish to share, should be open to all staff. I don't wish to have separate Document Libraries.
How can I achieve this seemingly simple task??
Thanks

Hi Paul - I have just tested that exact scenario you suggested again as I was hoping I had done something wrong in my previous testing and that it was in fact that simple.
Here's my problem though, but first the steps I followed so you can tell me if I did anything wrong:
1) Stop inheriting permissions on Document Library
2) Remove groups (other than admin type groups) from Document Library
3) Login with normal user (Lets call him Bob) - he cant see (hence browse) the Document Library at all and gets a permission denied when explicitly browsing to the Document Library URL.
4) Create a test Word file under root of Document Library - called Wordtest1.docx
5) Create a test Folder under root of Document Library and inside that folder create a second test Word file called Wordtest2.docx
6) Share the root Testword1.docx file with Bob. Bob can open this file via direct URL but cant browse the file because the Document Library URL still shows as no permission.
7) If I change the permission on the Document Library to allow "View" access then he can browse the files....but then via Office Web Apps he can also see inside every single document in the Document Library (even those not shared with him) which
is pointless.
8) PS: The reason I created the folder structure in point 5 above is that I found that if I have the Document Library as a web part on the main page of the Department site, I can see the file that has been shared with me. Yay. But if I share the file that
is in a folder within the Document library that file does not display and hence I cant see it or browse to it. F%$#
I really hope you can show me the error of my ways but I just cant see how I can achieve this which puts my whole SharePoint roll-out in huge jeopardy.
eim-operator - with regards the "shared with me" option on their personal page, correct me if I am wrong but this needs to be an additional 3rd party app as its not currently available on a Sharepoint on-premise solution, right?

Similar Messages

How to track the sharepoint documents from MS Dynamics end???

Hi,
I want to track the SharePoint documents from MS Dynamics CRM end.
When the document is added or deleted i need to show the message that docuement is added at so and so document library.
If i use event receivers what else i need to do after that.
Any suggestions or solution for/on this.
Thanks,
Jiteendra SapathiRao.
Jitendra.S

Hi,
To track the added or deleted event of a SharePoint Library, I would suggest you use workflow which can be triggered when there is file added or deleted, then we can send an
email for notification.
Send email in a workflow:
http://www.youtube.com/watch?v=nNxD82KiUhQ
Best regards
Patrick Liang
TechNet Community Support

Create a new document in Sharepoint Document Library/OneDrive on iPad/Safari

Hi,
My users are having trouble creating a new document from OneDrive in Safari on their iPads. The screen goes grey like its going to show the popup to select the new file type, but the popup never comes up. If they clear their cache, it works for exactly 1
time and then goes back to this behavior. I'm not exactly sure if it worked before and/or when it stopped working. The iPad I have tested was at the latest 8.2 version of IOS and my Sharepoint farm is an On-Prem install of 2013 with SP1 mark2. My WAC farm
is also 2013 SP1.
Any suggestions?
Thanks,
Matt

Hi,
I understand you are suffering the issue when create a document in Sharepoint Document Library/OneDrive on iPad.
According to the official article
https://technet.microsoft.com/en-us/library/fp161353.aspx?f=255&MSPPError=-2147217396, the version of your iOS should be in the supported list. I guess the issue may start after you installed an update, and if there is any other version (low versions)
of iPads in your company, please use a different version device to test the issue.
Meanwhile, to determine whether the issue is related to your SharePoint environment, I suggest you just to register an Office 365 trail account, and test the issue with SharePoint Online. In case the same issue happens with SharePoint Online, the issue should
be related to your client device, and my next suggestion is to contact support of your device manufacture.
Once you need any help from SharePoint end, please don’t hesitate to come back, and we are always happy to support you.
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

How to show sharepoint documents in salesforce ?

How to show sharepoint documents in salesforce ?
I should also be able to upload documents from salesforce directly to sharepoint document library/list if the users attach a document for a record in salesforce. Any idea how to achieve this?
What are the things need to be done if my sharepoint is available in intranet Or if it is SharePoint Online , how can we link this to salesforce (as Salesforce is global and can be accessed from anywhere). What are the security measures that I need to look
at and how to achieve this?
Ex:- I have a record in salesforce account object. I have to attach a document for that record which should be directly uploaded to sharepoint and shouldn't exist in salesforce, but it should display the listview to the users once its uploaded to sharepoint
and they should see them as if they exist inside salesforce, once they click on the link in the listview of the relatedlist, it should open the document from sharepoint.
Thanks in advance.

Hi,
According to your post, my understanding is that you want to show SharePoint documents in salesforce.
You need to integrate SharePoint with Salesforce.
Nick Swan
has written an article on how to integrate Salesforce and SharePoint 2007 through the Business Data Catalog.
But it might be useful as the theory is the same for using SharePoint 2010 and the Business Connectivity Services:
Salesforce and SharePoint
Outside of that, there are some useful third-party products you can have a look at.
Cloud Connector: http://www.layer2.de/en/community/FAQs/cloud-connector/Pages/Office-365-Salesforce-Integration-Migration-Replication.aspx
DocAve Data Replication: http://www.avepoint.com/salesforce-data-replication/?gclid=CNjZ8sGwl6kCFYEc4Qod-xD-uQ
DataZoom Script: http://www.siafoo.net/snippet/261
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Not able to create sub folder using SharePoint web service in large SharePoint document library (Item count view threshold limit)

We are trying to create folder & subfolder in a SharePoint document library using SharePoint default(dws) web service. Document library has unique permission as well as item level permission. It was working as expected. Once item count crosses
view threshold limit ( 5000) , create folder web method completes with an error and it creates a folder in SharePoint.
Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dws="http://schemas.microsoft.com/sharepoint/soap/dws/">
   <soapenv:Header/>
   <soapenv:Body>
      <dws:CreateFolder>
         
         <dws:url>Shared Documents/VenTest02092015v1</dws:url>
      </dws:CreateFolder>
   </soapenv:Body>
</soapenv:Envelope>
Response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body>
      <CreateFolderResponse xmlns="http://schemas.microsoft.com/sharepoint/soap/dws/">
         <CreateFolderResult><Error ID="2">Failed</Error></CreateFolderResult>
      </CreateFolderResponse>
   </soap:Body>
</soap:Envelope>
While trying to create subfolder under the above created folder service throws an exception saying
FolderNotFound.
Though we are able to create subfolder from SharePoint UI successfully.
Request
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dws="http://schemas.microsoft.com/sharepoint/soap/dws/">
   <soapenv:Header/>
   <soapenv:Body>
      <dws:CreateFolder>
         
         <dws:url>Shared Documents/VenTest02092015v1/REQ-1</dws:url>
      </dws:CreateFolder>
   </soapenv:Body>
</soapenv:Envelope>
Response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body>
      <CreateFolderResponse xmlns="http://schemas.microsoft.com/sharepoint/soap/dws/">
         <CreateFolderResult><Error ID="10">FolderNotFound</Error></CreateFolderResult>
      </CreateFolderResponse>
   </soap:Body>
</soap:Envelope>

Yes, you're probably hitting the 5000 list item threshold (
http://sharepoint.stackexchange.com/questions/105937/overcoming-5000-file-document-library-limits ). I assume you can do it via the UI because you're probably logged in as an admin in which case, out of memory, the threshold is 20.000 items. You can extend
this limit, but you probably shouldn't.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Ssrs sharepoint 2013 error: "A delivery error has occurred ...not a sharepoint document library..."

Greetings SSRS/SharePoint experts,
SharePoint 2013 with SSRS - Creating a subscription to a report that is in SharePoint
I'm trying to create a subscription to publish a report to a sharepoint document library.
I've configured all the settings and on clicking OK get the following error:
"A delivery error has occurred. ---> Microsoft.ReportingSerives.Diagnostics.Utilities.DeliveryErrorException: A delivery error has occurred. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidExtensionParameter: One of the extension
parameters is not valid for the following reason: The delivery path is either not a SharePoint Document Library Folder or does not exist in the Share Point farm."
SQL Server Developer Edition 2012 SP1
SharePoint 2013 Standard
Just wondering if anyone has a solution.
I've tried changing the proxy settings as per this post
http://social.technet.microsoft.com/Forums/en-US/19817dc7-6725-40d8-befa-1b94099a71bd/sql-server-2012-reporting-services-in-sharepoint-2013-integrated-mode-dilivery-extension
Workaround is to not use a sharepoint document library but write the report to a windows file share (this works but is not optimal).
Hoping someone at Microsoft or an expert will come back with something.
Kind regards
Gio

Hi,
Can you check the SharePoint ULS log located at : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS, and look at the log there when the error occurs?
You can also check the Application Event Log on the SQL Server to see if there are any additional errors.
Tracy Cai
TechNet Community Support

Download older version of a file from SharePoint Document Library using CSOM and 404 error

Hi,
I am trying to download previous versions including Major and Minor versions of documents from SharePoint Online using CSOM. I get 404 error when I try to download the file. I found several posts on various discussion forums where people are getting same
error but none of those have any solution/answer. Below is one of the threads and sample code I have tried that results in 404 error. If I use the link in browser directly, I am able to download the file. Also I am able to download the current version of file
using CSOM without any problem, it is only the older versions that give me 404 in CSOM.
http://qandasys.info/how-to-download-the-historical-file-version-content-using-csom/
public int GetStreamFromFile(string docid, string lib, string fileurl, ClientContext clientContext, int iuserid, string Version, bool isCurrrent)
if(!isCurrent)
List LibraryName = clientContext.Web.Lists.GetByTitle(lib);
clientContext.Load(LibraryName);
clientContext.ExecuteQuery();
CamlQuery camlQuery = new CamlQuery();
camlQuery.ViewXml = "" + fileurl +
Microsoft.SharePoint.Client.ListItemCollection collListItem = LibraryName.GetItems(camlQuery);
clientContext.Load(collListItem, items => items.Include(item => item.Id, item => item["FileLeafRef"], item => item["LinkFilename"],
item => item["FileRef"], item => item["File_x0020_Size"], item => item["DocIcon"], item => item.File.Versions));
//clientContext.Load(collListItem);
clientContext.ExecuteQuery();
foreach (Microsoft.SharePoint.Client.ListItem oListItem in collListItem)
//string fileurl1 = (string)oListItem["FileRef"];
//string filename = (string)oListItem["LinkFilename"];
foreach (FileVersion version in oListItem.File.Versions)
if (Version == version.VersionLabel)
//Added excutequery to get object one more time as per blog
//http://social.technet.microsoft.com/Forums/de-DE/sharepointdevelopmentprevious/thread/88a05256-8694-4e40-863d-6c77512e079b
clientContext.ExecuteQuery();
FileInformation fileInformation = ClientOM.File.OpenBinaryDirect(clientContext,version.Url);
bytesarr = ReadFully(fileInformation.Stream);
Darwaish

Hi,
According to your description,
I know you want to get older version of a file from SharePoint Document Library using Client Object Model.
The following code snippet for your reference:
public void GetVersions()
ClientContext clientContext = new ClientContext(“http://SPSite”);
Web site = clientContext.Web;
clientContext.Load(site);
clientContext.ExecuteQuery();
File file = site.GetFileByServerRelativeUrl(“/Shared Documents/mydocument.doc”);
clientContext.Load(file);
clientContext.ExecuteQuery();
ListItem currentItem = file.ListItemAllFields;
clientContext.Load(currentItem);
clientContext.ExecuteQuery();
FileVersionCollection versions = file.Versions;
clientContext.Load(versions);
clientContext.ExecuteQuery();
if (versions != null)
foreach(FileVersion _version in versions)
Console.WriteLine(“Version : {0}”,_version.VersionLabel);
More information:
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.file.versions.aspx
Best Regards,
Dennis Guo

Advice needed for provider hosted web application - authentication and access to SharePoint document library

I haven't done SharePoint 2013 development with claims so I apologize in advance if my assumptions and questions are way out in left field.
I'm trying to understand SharePoint 2013 claims authentication for a scenario that involves:
A SharePoint provided hosted (web forms) app that will pull information and assets (e.g. PDFs) from SharePoint into the web page.
It will be a VS 2012 solution with asp.net.identity feature.
Security will be set for internal users, federated external users and forms-based external users. Based on their security and (claim type) role it will define what information and assets that can be retrieved from SharePoint
I have looked through MSDN and other sources to understand.
This one helped with my understanding
Federated Identity for Web Applications and assumed that the general concept could be applied to forms-based identity for non-Federated external users .
What I have now:
VS 2012 solution web forms application set to Provider Host with asp.net.identity feature and its required membership tables.
I can create new users and associate claims to the new user.
I can log in with a user from the membership tables and it will take me to a default.aspx page. I have added code to it that displays the claims associated to a user.
For POC purposes I'd like to retrieve documents that are associated to this user from the default.aspx page.
This is where I am having trouble understanding: Is my understand correct?
Internal users
since they are internal on the network i am assuming that they would already have access to SharePoint and they would already be configured to what documents that they have available to them.
Federated external users & Forms authentication external users
it seems to me that the authentication for external users are separate from SharePoint authentication process.
changes to the configuration settings are necessary in SharePoint, IIS, web application.
I believe this is what i read.
claims processes (e.g. mappings) need to be set up in SharePoint
as long as external users are authenticated then things are ok b/c they would have claims associated to the user and the configuration in SharePoint takes are of the rest.
This statement bothers me because I think it's wrong.
So basically i'm stuck with if my understanding is correct: once a user is authenticated either by federated identity or asp.net.identity authentication that it should go to the provider hosted default.aspx page because the claim is authenticated and means
that it should have access to it and the SharePoint document library based on some claim property. I could then write the calls to retrieve from a document library and SharePoint will know based on some claim property that the logged in user can only
access certain documents.
It just sounds too good to be true and that i'm missing something in the thought process.
Thanks in advance for taking the time to read.
greenwasabi

Hi GreenWasabi,
i agree this is an interesting topic to discuss,
as you can check from the article, you may check this example from the codeplex:http://claimsid.codeplex.com/
when i thinking regarding this topic, its looks like an environment with multiple of realms,
from what you understand, its correct that all the authentication is based from the provider, so for example i have a windows live ID and internal ID, then when i login windows live ID, it will be authenticated using windows live ID server.
here is the example for the webservice:
http://claimsid.codeplex.com/wikipage?title=Federated%20Identity%20for%20Web%20Services&referringTitle=Home
as i know, if you using this federated, i am not quite sure that you will need to go to the provider page literally, perhaps you can check this example if we are using azure:
http://social.technet.microsoft.com/wiki/contents/articles/22309.integrating-windows-live-id-google-and-facebook-accounts-with-sharepoint-2013-white-paper.aspx
Regards,
Aries
Microsoft Online Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Save output of powershell script to a SharePoint document library?

Hi
I've got the PS script below which scripts out our SQL replication so disaster recovery. Is there a way to output this to a SharePoint document library so that way we can version control the file to keep multiple copies and it also avoids outputting
this to a file share. We would still need to have the files with the .sql extension format which is an allowed file type in our farm.
Thanks
#Load command-line parameters - if they exist
param ([string]$sqlserver, [string]$filename)
#Reference RMO Assembly
[reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Replication") | out-null
[reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Rmo") | out-null
function errorhandler([string]$errormsg)
    writetofile ("-- Replication Script Generator run at: " + (date)) $filename 1
    writetofile ("-- [Replication Script ERROR] " + $errormsg) $filename 0
function writetofile([string]$text, [string]$myfilename, [int]$cr_prefix)
    if ($cr_prefix -eq 1) { "" >> $myfilename }
    $text >> $myfilename
function initializefile([string]$myfilename)
    "" > $myfilename
trap {errorhandler($_); Break}
#Deal with absent parameters
[string] $hostname=hostname
if ($sqlserver -eq "") {$sqlserver = read-host -prompt "Please enter the server name or leave blank for Hostname"}
#if ($filename -eq "") {$filename = read-host -prompt "Please enter the file name (eg 'c:\ReplicationBackupScript.sql')..."}
if ($sqlserver -eq "")   {$sqlserver = $hostname}
if ($filename -eq "")   {$filename = "d:\Rep\CreateReplication-$(get-date -format ddMMyyyy).sql"}
# Clear file contents
if (Test-Path ($filename)) {Clear-Content $filename}
$repsvr=New-Object "Microsoft.SqlServer.Replication.ReplicationServer" $sqlserver
initializefile $filename
# if we don't have any replicated databases then there's no point in carrying on
if ($repsvr.ReplicationDatabases.Count -eq 0)
    writetofile ("-- Replication Script Generator run at: " + (date)) $filename 0
    writetofile "-- ZERO replicated databases on $sqlserver!!!" $filename 1
    EXIT
# similarly, if we don't have any publications then there's no point in carrying on
[int] $Count_Tran_Pub = 0
[int] $Count_Merge_Pub = 0
foreach($replicateddatabase in $repsvr.ReplicationDatabases)
        $Count_Tran_Pub = $Count_Tran_Pub + $replicateddatabase.TransPublications.Count
        $Count_Merge_Pub = $Count_Merge_Pub + $replicateddatabase.MergePublications.Count
if (($Count_Tran_Pub + $Count_Merge_Pub) -eq 0)
    writetofile ("-- Replication Script Generator run at: " + (date)) $filename 0
    writetofile "-- ZERO Publications on $sqlserver!!!" $filename 1
    EXIT
# if we got this far we know that there are some publications so we'll script them out
# the $scriptargs controls exactly what the script contains
# for a full list of the $scriptargs see the end of this script
$scriptargs = [Microsoft.SqlServer.Replication.scriptoptions]::Creation `
-bor [Microsoft.SqlServer.Replication.scriptoptions]::IncludeEnableReplicationDB `
-bor [Microsoft.SqlServer.Replication.scriptoptions]::IncludeCreateLogreaderAgent `
-bor [Microsoft.SqlServer.Replication.scriptoptions]::IncludePublicationAccesses `
-bor [Microsoft.SqlServer.Replication.scriptoptions]::IncludeArticles `
-bor [Microsoft.SqlServer.Replication.scriptoptions]::IncludePublisherSideSubscriptions `
-bor [Microsoft.SqlServer.Replication.scriptoptions]::IncludeSubscriberSideSubscriptions
writetofile ("-- Replication Script Generator run at: " + (date)) $filename 0
writetofile "-- PUBLICATIONS ON $sqlserver" $filename 1
writetofile "-- TRANSACTIONAL PUBLICATIONS ($Count_Tran_Pub)" $filename 1
foreach($replicateddatabase in $repsvr.ReplicationDatabases)
    if ($replicateddatabase.TransPublications.Count -gt 0)
        foreach($tranpub in $replicateddatabase.TransPublications)
            writetofile "/********************************************************************************" $filename 0
            writetofile ("***** Writing to file script for publication: " + $tranpub.Name) $filename 0
            writetofile "********************************************************************************/" $filename 0
            [string] $myscript=$tranpub.script($scriptargs)
            writetofile $myscript $filename 0
writetofile "-- MERGE PUBLICATIONS ($Count_Merge_Pub)" $filename 1
foreach($replicateddatabase in $repsvr.ReplicationDatabases)
    if ($replicateddatabase.MergePublications.Count -gt 0)
        foreach($mergepub in $replicateddatabase.MergePublications)
            writetofile "/********************************************************************************" $filename 0
            writetofile ("***** Writing to file script for publication: " + $mergepub.Name) $filename 0
            writetofile "********************************************************************************/" $filename 0
            [string] $myscript=$mergepub.script($scriptargs)
            writetofile $myscript $filename 0

Check out Using PowerShell to upload a scripts output to SharePoint
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Linking a programmatically created folder in SharePoint Document Library.

I have created folders within a document library using InfoPath & C#. To that folder I uploaded several documents using several file attachment controls within the same InfoPath Form using the code behind the form. Now I want to create an Hyperlink
to each folder in another document folder's column that has the relationship with the previously created folder.
When I googled I saw there are lot of articles to create Folders ,uploading documents to folders in a SharePoint Library but I cannot understand how to create a hyperlink in a SharePoint Document Library field column.
Could someone help me to solve this matter?
Thanks,
Regards,
Chiranthaka

Why don’t you create a hyperlink column to store the hyperlink value, or you can use a lookup column to lookup the related folder item?
Qiao Wei
TechNet Community Support

Word opening in Client Application in SharePoint document library when feature is not activated in manage features in site collection

Hello, I wish for all Word documents to open in the browser for my SharePoint document library on my team site.
The feature 'open in client application' is not activated in Features for the site collection and the setting in the document library is set on 'Use the server default (open in the browser)
When I select File > new> from the ribbon in the document library - it still opens Word in the client application?
Any ideas on this?
Is there a general Office 365 setting over riding SharePoint somewhere?
Regards
kegan1

Okie don't open up a ticket. Can you please open internet explorer...See if its the latest version. Once you have done that can you login to the SharePoint site. Then go to the internet wheel option in top right corner > select manage add on >
Click on toolbars and extensions on left > then click on SharePoint open documents in client and disable it. Close the browser completely now for the changes to take effect. Open internet explorer once again and then try to go to site collection click on
file and create new. The word will open up in browser now. This has to be done on each and every machine in your firm so that users will be able to open up only in browser. Out of the box there is only one way is to customize the ribbon and remove the new
option from there or creating an all together new ribbon for your SharePoint from visual studio.

Attaching Attributes to Image For Loading to SharePoint Document Library

We currently have a need to create a searchable document library which will consist solely of images. The standard metadata for a file/image won't suffice in this case. We have some custom attributes that will need to be searchable.
Essentially, we will have a library of receipt images for expense reporting purposes. We get these images from a third party who handles all of our expense reporting. There are two large zipped files we receive: one file contains all the actual expense report
"data" that was processed that day(amount, date, client, job, etc.) and the second file contains all the receipt images for those expense report items. Each data file contains data for individual expense reports, and each expense report is assigned
a unique ID. Each line item in an expense report is also assigned a unique ID. Lastly, each receipt image for a line item of a specific expense report is also assigned a unique ID.
The zipped image file only contains images. There is a main image file - this contains several smaller zipped files. Each of the smaller zipped files contains all receipt images for a specific expense report. Each image file name is comprosed of three parts:
The expense report identifier, the unique image identifier, and the expense report line item identifier.
So, to put this all into perspective:
On Thursday, we received an image file named extract_images_p006320452r3_20140904171423
This file contained images for the following unique expense reports:
The compressed file 95FB8C488519427793FC contains the following receipt images:
The "data" file - as mentioned before - contains the actual info about the expense and image. These include: date of transaction, date approved, vendor, amount. GL code, type, function, client, project, billable or not, and several other attributes.
All of this information - including the location of the images - is stored in a SQL Server database and then placed in an SSAS cube.
The images are related back to the underlying data via the expense report id, and line item id.
What I need to be able to do is to somehow "tag" these images with all their underlying attributes, load then into a SharePoint document library, and make them searchable.
I have already figured out that I would need to create several SharePoint lists based on the available values in my OLAP cube (essentially a dataset each for clients, vendors, etc.). The part I have no idea how to accomplish is how to tag each image with
its respective information.
All the pertinent info is stored in the database tables, just don't know how to attach it to each image.
Hopefully, this made some kind of sense. If anyone has any idea on how to even remotely accomplish such a thing, your input would be greatly appreciated!
Thanks in advance!
A. M. Robinson

You will have to develop a custom solution to do this. I am assuming you have taken the first steps to define separate document libraries for the expense reports and images along with site columns and contenttypes. You would define the site columns based
on the data you want to search on and assign these to corresponding contenttypes. So basically a contenttype for expense reports and receipts possibly. You would link the two contenttypes using the expense report id.
Your custom solution would have to break apart the zip files and upload and index (set site column data) for each file. Then the user could search on the expense report id and get all the files associated with the expense report.
An alternative could be to use one document library and have all the files uploaded into their own document set (folder).
Blog | SharePoint Field Notes Dev Tools |
SPFastDeploy | SPRemoteAPIExplorer

Upload a document from a form into a SharePoint document library

The idea is that I have a form which I want to allow users to upload files into my SharePoint document library. I am just not just what to do after the 'HasFile' Statement. Some small snippets of my code below. I am just not sure how from the fileupload ID
to get it into my document library. Please provide code.
<asp:FileUpload ID="FileUpload1" runat="server" />
<asp:Button ID="Button1" runat="server" Text="Button" onclick="Button1_Click" />
Server side code
protected void Button1_Click(object sender, EventArgs e)
if (FileUpload1.HasFile)

protected
void
Button1_Click(object
sender,
EventArgs
e)
   if
(FileUpload1.HasFile)
        // Assuming you have list current context. Or else get reference to the list instance from the parent SPWeb     var list
= SPContext.Current.List;
     list.RootFolder.Files.Add(FileUpload1.FileName,
FileUpload1.FileBytes).Update();

Load a project from a SharePoint document library

"Add a project to a SharePoint document library" is nicely documented in the RoboHelp reference guide. However there is no information on adding another user to that library, i.e. how do you synchronize that user with the library on SharePoint? Do they open a new project and restore the files...? I have no idea how to do this - spent the last 2 hours trying to figure this out as there in no information on this - not even on Google searches. It's really a shame that a powerful help authoring tool is lacking help itself. I'm a fan of robohelp, however when you face roadblocks like this - it's very frustrating. This should be something simple to do and it should be clearly documented. Can someone please help.

I have just found the solution and it had previously been answered in this post: How do I connect multiple users to a project on Sharepoint for collaboration
Adobe - you need to include this in your documentation - this is a vital feature for people using the ShrePoint connector. I should't have to take two hours of my time to find a random post about this to resolve my problem.

Adding a Sharepoint Document Library in Windows Explorer Fovorites

I want to add a sharepoint document library in my favorites in windows explorer... Every time I copy the link, instead of opening the library in windows explorer, it open the browser and go directly to the site... Any help would be appreciated.
Thanks in advance,
Sebastien

Hi Seabass:
Have you tried mapping the library in question as a network location on your local machine?
http://windows.microsoft.com/en-us/windows/create-shortcut-map-network-drive#1TC=windows-7
To map to a particular SharePoint resource on your site, you would use this structure:
\\mysharepointsite@80\sites\library\Photos as your network address.
In this manner, you can add this link to your Favorites, and you will have the Windows Explorer mode you're requesting. Hope this helps! ;)

SharePoint Document Permissions?

Similar Messages

Maybe you are looking for