I'd like to force sharepoint to save files in directory. Is there a way to do that?
I think about this scenario: users upload files to some list / library in sharepoint and automatically or by pushing "publish" the files are copied to some local server's directory.
Edit:
In other words i would like to connect sharepoint library with physical directory in server that runs IIS, so that files uploaded to library were seen in that folder.
I'm new to sharepoint.
Are you talking about Remote BLOB Storage? I have not tried this and assume that RBS can be enabled for a Site level only and not for individual document libraries. If you want this for a particular doc library, you can write an event handler to save the uploaded documents to file system and then remove the uploaded file.
Most likely you don't want to do this. If you're doing it in order to access the files from other applications, or having them show up in a users home directory or something, you can just map the document library as a network drive/web folder.
Related
I am trying to save log files to the user/documents directory on corporate client laptops running Windows 10 but if oneDrive is active, it grabs the entire documents folder structure. It is impossible to know if the laptops have onedrive or not.
Question: Is there a way to bypass onedrive and save to the local documents dir?
Currently I am having to test if the client has onedrive or not.
It would be helpful if I could make the code agnostic about this issue and always save to local user documents directory.
We tried to migrate 5GB of files from SVN to Sharepoint which has many nested folder structures. To perform this we have downloaded files from SVN and used sharepoint web portal to upload as "Folder". I have selected the root folder where it has 5GB of files. It was processed for few hours and ended without any errors. Or I dont know where I am supposed to look for errors. After folder upload when I perform random validation, found that many folders are incomplete and did not find expected files in those folders.
I have searched in internet found that below tool is available for local sharepoint to Microsoft 365. Is there any other tool or the steps to upload local files to sharepoint.
https://learn.microsoft.com/en-us/sharepointmigration/introducing-the-sharepoint-migration-tool
What we tried - We selected an entire root folder of 5 GB size which had many subfolders and files inside it to upload it to sharepoint through upload folder option.
Expected Result - All the subfolders and files inside the root folder should get uploaded on sharepoint
Actual Result - We found that some of the files and subfolders from the root folder did not get uploaded on sharepoint and the job had completed without any error being thrown or maybe I don't know where am I supposed to look for errors.
You can try File shares to Migrate your on-premises file share content to Microsoft 365.
Go to SharePoint admin center-->Migration-->File shares.
For more information, please refer to:
https://learn.microsoft.com/en-us/sharepointmigration/mm-get-started
Having installed onedrive on Ubuntu I have noted that the monitor function works quite well but does not maintain the directory structure on the remote onedrive system. I have two directories defined in the local onedrive folder. If I create or copy a document into one or other of these directories then onedrive monitor will upload it to the remote server but they appear at the top level and not in synced folder from which they came. Is there a way to configure onedrive to have it respect the source directory structure?
Having installed onedrive on Ubuntu
Hopefully you followed the correct installation procedure as documented here: https://github.com/abraunegg/onedrive/blob/master/docs/ubuntu-package-install.md
I have noted that the monitor function works quite well but does not maintain the directory structure on the remote onedrive system. I have two directories defined in the local onedrive folder. If I create or copy a document into one or other of these directories then onedrive monitor will upload it to the remote server but they appear at the top level and not in synced folder from which they came.
This is very odd - as, the folder that is containing those document is what should be replicated to OneDrive online.
Please follow the correct support process as detailed on GitHub: https://github.com/abraunegg/onedrive
I created a Logic App that uses the Sharepoint trigger "When a file is created or modified in a folder". It works perfectly when I upload a file in Sharepoint online (in a Sharepoint browser tab). But, it doesn't work when I drop a file in my synced Windows explorer folder.
I read that someone faced the same problem: https://learn.microsoft.com/en-us/answers/questions/41215/logic-app-why-does-sharepoint-file-properties-trig.html. Here it says:
Move files and flow runs When you move one or more files from one
document library to another, the original file is moved from the
source library to the destination library. Moving the file does not
alter any custom metadata, including when the file was created and
modified. Hence, this action does not trigger any flows for those file
updates associated in the library where it was moved.
Syncing files to your OneDrive for business and SharePoint document
libraries When users sync one or more files from one document library
to another, the original file is moved (synced) from your client to
the destination library. Syncing the file will not alter any custom
metadata including when the file was created and modified. Hence, this
action will not trigger any flows for those file syncs in that library
or in your OneDrive for business.
The thing is that I NEED this Logic App to run by just dropping this file in a Windows Explorer folder (which is a Sharepoint folder shared with a certain person). Do you know how can I achieve this?
It started working for me when I used the OneDrive - When a file is created Connector because we use OneDrive for Windows Explorer and need to include the folder where the trigger should be invoked. We must set Include subfolder to true if we want the trigger to be fired while adding any file to the subfolders.
Here are the screenshots of the logic app working
When adding file in subfolders
When adding file in root folder
I want to find the correct place to save my user settings for my uwp app. I know there exists:
local: Data that exists on the current device and is backed up in the cloud
roaming: Data that exists on all devices on which the user has installed the app
temporary: Data that could be removed by the system any time the app isn't running
-localcache: Persistent data that
exists only on the current device
I can access the above places with ApplicationData.Current. Which are located somewhere in C:\Users\bla\AppData\Local\Packages\1e7e-94a6-4235-a0c5-9b143f8b_8webbwe
The project also contains a Asset folder, and I can't find a good source which tells me where the folder is located when the app is installed (not in developer mode).
Some developers place there settings into the asset folder. Why? What's the advantage? Is there also a file size limit like for ApplicationData.Current ? When deploying a settings folder into the asset folder will it be available for all user which installed my app? Any background informations regarding the asset folder are appreciated.
Settings files are most appropriate in the ApplicationData folders or ApplicationData.LocalSettings or .RoamingSettings See Store and retrieve settings and other app data
The assets folder is purely a convention. The "assets" name is not special other than to suggest what types of files go in the folder. It is just a useful way to organize the application package to have a place for assets (images, etc.) that are used in the app.
When the app is installed the assets will be in the Package.InstalledLocation directory and can be addressed with an ms-appx:///assets/ URI. Typically this will end up somewhere in \Program Files\WindowsApps\.
Putting a settings file in assets would be a bad idea as the InstalledLocation is read-only and as settings are user data.
There is no hard size limit for files in ApplicationData folders, although if too much data is stored in RoamingFolder then it won't roam. The files will still be available locally.