New answers tagged

1

Well, it looks like I was doing a few things wrong. The ColdFusion language I use passes arguments as a structure, the order does not matter. This appears to not be the case for Sharepoint. ex: files/add(overwrite=true,url='#arguments.filename#') is not the same as files/add( url='#arguments.filename#'; overwrite=true; ) I also had [;] ...


0

From what I could find, in order to perform operations on Office 365, we need to authenticate using claims-based authentication, which is done in not one, but a series of sequential steps. build a SAML request submit a SAML token request to Microsoft Online Security Token Service receive a signed security token POST the token to SharePoint Online receive ...


0

Well, it looks like I was doing a few things wrong. The ColdFusion language I use passes arguments as a structure, the order does not matter. This appears to not be the case for Sharepoint. ex: files/add(overwrite=true,url='#arguments.filename#') is not the same as files/add( url='#arguments.filename#'; overwrite=true; ) I also had [;] ...


0

Another option is FileCreationInformation... function File Upload(ClientContext ctx, string folderRelativeUrl, string fileName, Stream data) { var ci = new FileCreationInformation() { ContentStream = fs.Value, Overwrite = true, Url = folderRelativeUrl + "/" + fileName }; var newFile = destinationInfo.Folder.Files.Add(...


1

public void UploadDocument_FromStream(Stream file, string fileName) { using (var clientContext = OpenConnectionToSharePoint()) { var webContext = clientContext.Web.Context; if (file == null) throw new Exception("Stream cannot be null"); if (webContext.HasPendingRequest) webContext.ExecuteQuery(); ...


0

This may not be what you're trying to do, but I wrote a c# console application that will upload documents from my local system to SharePoint while setting the appropriate meta data for our organization (via the Microsoft.SharePoint.Client.Online.CSOM nuget package). Unfortunately, I can't share the code in full, but I can share enough to give you a really ...


2

going from 50MB to 100MB, i dont see major issue. But couple of things to keep in mind. it will increase traffic from User to wfe to SQL. You have to monitor the performance on the servers. Plan the database space, as you increasing the file size Do the Load testing before hand to check if your farm is ok for the this increase. if you have the Antivirus ...


2

Some of the one I can think of is Files are stored in the database and it will grow as you put large files DB size will affect backup and restore strategies You can try using RBS as a workaround Apart from that I think there won't be any other issues.


0

TLDR: you need to use the server relative URL, even though the context includes the site information. I had this same issue, and resolved it by using Fiddler. When I used the client Object Model, I created the context with the site path, i.e. "https://server/sites/siteName", then var docs = web.Lists.GetByTitle(documentLibraryName); SP.File uploadFile = ...



Top 50 recent answers are included