User Profile
JR2021
Brass Contributor
Joined Apr 11, 2017
User Widgets
Recent Discussions
Re: Windows Account Sync Known wifi Network at Device level
Thank you! I can find very little information about this and it's a huge security risk and privacy concern. We are seeing users across the company gaining access to the login information of private home wireless networks (including passwords!) of other users and it's unacceptable, and there is no clear way to disable this. Maybe turning off the Windows backup for "Accounts, WiFi networks, and passwords" will work, but I assume this then forces us to disable the password keychain and other helpful features? Why? Why on earth is all of that lumped up under a single checkbox? Why isn't there at the very least a registry key to let us disable just the wireless network syncing? Why are wireless networks and passwords being shared with and accessible by every user to begin with and not just the user who added? Does this mean all of the other backed up information under that checkbox is also accessible by every user on a device? Microsoft's implementation of this has created enormous risk and vulnerability for any workers who share devices other people, and judging by the sparse amount of discussion I can find about this concern, I think most people don't even realize it. I fail to understand how anyone at Microsoft could have considered this to be a good idea, especially since they like to portray themselves as so security conscious.456Views3likes0CommentsRe: "Edit in grid view" for selected people
Meow13 Take a look at this guide https://tayfuntech.com/2021/08/15/edit-grid-view-option-disappears-in-sharepoint/ It's for granting access to grid view for external users, but you may be able to figure out a way to use the same premise to configure permissions for groups on the library to your liking. If you want to add or remove a single permission to a role (for example, the UI automatically checks off others when you select EditListItems permission), you can do that using Add-PnPRoleDefinition or Set-PnPRoleDefinition in the PowerShell PnP library. *edit* My thinking is that you could this by creating folders in the library to share with this group (let's call it "No Grid Group" for now) to work out of. Then you would break the library inheritance, remove the EditListItems permission from "No Grid Group" by giving that group a custom Role without EditListItems at the library level, and then you'd share the folders with "No Grid Group" for them to work out of and be unable to use grid view. I haven't tested it myself, and my example may require some tweaking, but you should be able to get it working since I have tested it with external users like the guide shows. Unfortunately, there's no simple switch you can flip for this.7.4KViews0likes0CommentsRe: Is there an API to read Microsoft forms data
waltksfc I needed the exact same thing, and thanks to you and ProtivitiDan I was able to figure out the correct path. If you want to make a custom connector for Forms in Flow, you'll need a way to handle authentication. Make a new app registration in Azure AD Use https://global.consent.azure-apim.net/redirect as the redirect Under Certificates & secrets, create a new client secret and save the value somewhere before closing the window because you won't see it ever again Under API permissions, add a permission. For this you'll want to go to the "APIs my organization uses" tab and find Microsoft Forms. Add it as a Delegated permission if you want the logged in user to only access their own forms in Flow. I haven't tried Application permission for Forms, but I imagine it will grant access to everyone's forms. If you don't want to have to approve every Delegated permission request, make sure after adding it that you press the "Grant admin consent" button. Take note of the Application ID. Open up Flow and create a custom connector using the App you just created. There are a lot of guides out there for how to make one. However, the relevant fields for this connector to work with Forms are: Host: forms.office.com Base URL: /formapi/api Identity Provider: Azure Active Directory Client id: your App ID from above Client secret: the value of the client secret from above Resource URL: https://forms.office.com Scope: your permissions from above (I used Forms.Read Responses.Read.All ) When you make the connector definition, you insert any dynamic parameters in curly brackets in the request URL. For example, to make an action that requests all questions that are on a specific form, you'd use https://forms.office.com/formapi/api/forms/{formId}/questions for the URL and then formId will be a parameter that you'd fill in for the Flow's action. I'm now able to authenticate to make web requests to Forms in a Flow so I know you'll be able to do it, too. Hopefully my little guide helps put you on the correct path!47KViews4likes0CommentsRe: deploy spfx command set for doclib is not working
Peter Cheung i know this is a late response, but this is to help anyone else having this problem since this question is surfaced in search results what you have to do is change the xml files in the spfx project found under sharepoint > assets in ClientSideInstance.xml change ListTemplateId (and in elements.xml change RegistrationId) from 100 to 101, so to make it show up in custom lists you use 100, and you use 101 to make it show up in document libraries if you need to use both at the same time, just copy and paste the xml chunks for ClientSideComponentInstance and CustomAction in their respective files here is a link with a more thorough description plus pictures: https://www.c-sharpcorner.com/article/sharepoint-framework-spfx-extension-add-list-view-command-set-to-list-docu3/ hopefully this saves someone some time 🙂2.8KViews0likes0Comments
Recent Blog Articles
No content to show