User Profile
David_Elsner
Brass Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Re: Pictures and Videos are not treated as "Documents" in Search IsDocument:true
Thanks, But I would like to have a query what returns all files (no folders) I thought that IsDocument:true is a query that returns all files, but it seems I was wrong? The pictures and videos where just an example - so your approach will work for them but maybe later I encounter other files that are also not treated as "Documents"? How can I be sure to return everything that is a file?Pictures and Videos are not treated as "Documents" in Search IsDocument:true
I have the need to search for all Files in a SharePoint Library (or globally). To do this I use the following KQL: IsDocument:true This works not for images. They do not seem to be "documents" in SharePoint. Whenever I search a library for IsDocument:true, I receive PDFs, Excel sheets, other office formats, but no pictures. Whenever I search for IsDocument:false, I get also the pictures from the list. This seems to be very strange to me. Any ideas how to change this behavior?Re: Get refresh token of Teams Desktop of the current user
Nivedipa-MSFT Thanks for your feedback. I am and was always aware that its not a good practice to use a refresh token for my use case. However, what I need to do is not available in the Graph. I want to add a cloud storage (or add document library) to a teams channel (no tab!), that users can navigate to it easily from within the channel. That's currently not supported with the Graph, only via the unofficial teams API. To call this API, I need always a user context (no client credential flow possible) So I am forced to a bad practice if I want to do what I need. So yes: Its a bad practice But no: A "good practice" seems not to exist here.Get refresh token of Teams Desktop of the current user
The Teams client must store access and refresh tokens somewhere (probably encrypted in the local or session storage of the underlying browser) I am wondering, if there is a way to read those tokens, especially the refresh token that Teams uses to call its Apis in the background. If I open the Teams developer tools, I can not find the token in any of the requests. And Fiddler seems to block Teams and there is no easy way to sniff the traffic produced by the client- do you have any other idea? Why do I need this? I need this token to write a script that uses the unofficial Teams api (not the graph). I want to use this API to create a link to a certain SharePoint library in all my Teams (it used to be called "Add cloud storage") This option is not available in the Graph and therefore I have to use the unofficial Teams Api to create those references programmatically. Getting a token for it (via authorization code flow) seems only possible with the Teams client itself.Edge: PDF files are opened with drawboard by default
A strange behavior happens to all PDF files on some of our computers. When we open a library on certain computers in the Edge browser, PDFs are opened by "Drawboard" what seems to be a software for PDF files. This is a newly installed machine with a user that does not have this problem on his other machine: Its definitely a client setting, because this happens for all users that login in this Edge instance. Any ideas how to change this back to the default behavior? We did not find anything...Users with Edit permissions cannot change permissions they created themselves
I noticed a very strange behavior of SharePoint today, that makes no sense to me. I created a normal SharePoint Teamsite (without a group) and added many people to the members group. This gives all those people "Edit" permissions. In this way they can also share files and folders with others through Direct Access. If a normal Edit-User shares something this works as expected: The folder is now shared with David and he gets permission to change the file. However, if the user wants to change those permissions afterwards, he has no permission to do this. The explanation is shown in the window: So users can give Edit-Permissions, but they need to be owners to remove those. This is contradictive to me. What is your experience? Any explanation?External user with Microsoft account still receives one time verification codes
We enabled the https://learn.microsoft.com/en-us/azure/active-directory/external-identities/one-time-passcode in our Azure Active Directory for external users. This works great and external users (without an MS account) can login with receiving the one time pass code. In the AAD this looks like this: You can see that the federation with "mail" has been added. However, if a user later creates a Microsoft account and associates his e-mail address with it, he still needs the one time verification code to log into our apps. If I delete the user form our AAD and re-invite him, I was hoping that the user can now use his MS account. But unfortunately the mail stays and the user always uses his one time passcode. Can you tell me how we can later switch to the MS Account login?Re: Should non-Office-working-files even go to SharePoint?
By the way- this is what Chat GPT answers, when I post the question to it: It's true that SharePoint and OneDrive may have limitations when it comes to working with non-Office files, such as Photoshop or CAD formats. While it's possible to upload these files to SharePoint, you may encounter issues when trying to open them in the browser or download them to the native application. One solution you mentioned is using the OneDrive-Sync client, which can work well for individual files or small folder structures. However, as you noted, it may not be the best solution for larger departmental collaborations due to sync errors and metadata issues. In terms of migrating only typical web files and Office documents to SharePoint and leaving the rest on the network drive, this could be a practical solution for your organization. By doing so, your employees can continue to work with those file formats in File Explorer, which may be more familiar and efficient for them. It may also reduce frustration and errors associated with trying to work with unsupported file types in SharePoint. That being said, it's worth considering the benefits of having all files, including non-Office files, in a centralized location such as SharePoint. This can improve collaboration, version control, and access to files across the organization. If there are specific business needs or workflows that require the use of non-Office files, you may want to explore other options, such as third-party plugins or integrations that can improve the handling of those file types in SharePoint. Ultimately, the decision to migrate only certain file types to SharePoint or to find a way to include all file types will depend on your organization's specific needs and priorities.Should non-Office-working-files even go to SharePoint?
There seems to be not a good solution out there for SharePoint + Non-Office working files. For example Photoshop or CAD formats cannot be opened from the browser and there is also no option to download them and open in the native application. I could use the OneDrive-Sync client, but if a whole departments collaborates in big folder structures, this also fails and leads to sync-errors. Also metadata and other things do not work here... We are tempted to only migrate typical web files (pdf, jpg, mp4) and office documents to SharePoint and leave the rest on the network drive. This is a lot less frustrating for the employees, because those file formats are much better embedded in file explorer. What is your opinion?Private/Public Folders of Department in Communicationpage and Teamsite?
Our departments have Private/Public folders on the network drive. The departments can read/write in both folders, but the public folder is accessible for everybody. If those folders are migrated to SharePoint, I am wondering if we should: - Create a Communicationpage for the public files - Create a normal Teamsite (without a group) for the private files - Connect both with a hub Collaboration will take place in MSTeams where drafts etc. will take place. The files are far below 100.000, so we could also: - Create a single Teamsite with two libraries: - Private library - Public library (unique permissions, everybody can read) What is better? Where are the pros and cons? AFAIK I am following the best practice of MS with the first approach. But two sites feed "too much" somehow...Unable to create personal views in whole tenant
Our users would like to create personal views in modern document libraries (SharePoint Online). But it does not matter which permission they have, nobody can add personal views. Even me - and I am a global admin - is not allowed to do so, but of course my permission level is telling me, that I have permission. What I find is, that all the time I save a new view I can only create public views. Other users with lower permissions are not able to create views at all. If I watch tutorials or screenshots from others they find the following option NOT greyed out: Any ideas what the cause of this could be?Tags with keywords in SharePoint
I know much about SharePoint metadata already. Also about the term store and the content type hub, where I can assign content types to many SharePoint pages. What I don't know is a smart way how to implement tagging. My scenario looks like this: 1. We have many SharePoint pages for our customer projects, each one for a machine we sold to a customer. 2. Sometimes failures in our customer projects happen. Those failures are repeating through many of our projects. 3. Each failure has a name 4. A failure can be described with different keywords in different languages. For example: 1. Name: Ram broke down Search terms: Ram break, Ram failure, Hopper leackage, Stempel fehlerhaft, ... 2. Name: Oil too hot Search terms: Oil issue, Öl zu heiß, Öl boiling 3. Name: Pressure too high Search terms: Pressure problem, Druck zu hoch, ... If a failure happens, people should be able to assign the Name of the failure to a set of files (a document set, a library or something similar) If other people search later for specific search terms, the cases should be found. For example: In ten different SharePoint pages I assigned the "Ram broke down" failure to a set of documents. If people are now searching for "ram failure", they should find all ten SharePoint pages, because "ram failure" is a search term for the failure "Ram broke down". However, with normal metadata something like this cannot be archived. One idea would be to use a managed metadata field for each failure and store all search terms below it. But assigning those to documents will be tedious, because all "search terms" have to be added manually. There must be a better idea... Do you have any alternative solution?
