Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
SharePoint
FUCK sharepoint
It's funny how it does everything but nothing well.
Seriously, I currently work with SharePoint for internal documentation and I audibly grunt every time I'm editing or managing anything using that thing.
We moved from S drive to SharePoint and I honestly don't know why
The reason is mainly money. SharePoint is cheap and a lot of companies already pay for it even if they don't use it.
SharePoint is also useful because it integrates seamlessly with teams.
It should be noted that SharePoint is designed for documents and not files.
You should think twice if you are replacing a file share with a SharePoint site because sometimes it will work terribly. CAD files for example is a terrible idea to put on a SharePoint site.
Here where I work we just sync with the user PC, like OneDrive, and the user can't tell the difference. For them it is just another folder in the Explorer. Some only access through Teams...
OneDrive and SharePoint are very similar in functionality. (In fact every personal OneDrive's is a SharePoint site) But SharePoint is intended to share files and other information while OneDrive is intended to be personal (with some limited sharing functionality).
Working with other colleagues and having all their files distributed on multiple OneDrive's is very inconvenient, while having a SharePoint is not.
why particularly CAD files? trying to understand why this is a bad idea as it appears that is where we are going
This thread explains it better than I could: https://www.reddit.com/r/sysadmin/comments/15q6hq4/psa_do_not_host_autocad_files_in_sharepoint/
SharePoint apparently has some kind of AutoCAD integration so it might work for you, but watch out. And most importantly don't just import the entire FileShare regardless of what it contains to a single SharePoint site.
The best that can be said of Sharepoint, is it could be worse, you could be using Notes.