2

Try following steps: Run npm i modernizr and then npm i @types/modernizr --save-dev. Then add its reference to config.json in externals{} like: "externals": { "modernizr": { "path": "node_modules/modernizr/src/modernizr.js", "globalName": "modernizr" } } Then reference the file in your WebPart.ts file like: ...


2

You can use Unified Audit Log in Office 365 to identify the user. In the Microsoft Admin center, you can navigate to https://protection.office.com/unifiedauditlog, add the URL of your site (append it with an asterisk) and you can filter the results.


2

In PowerApps managed metadata column shows up as a drop-down menu and There is no (out of the box) way to show the "tree structure" of terms. Source: PowerApps and managed metadata. Multi-valued managed metadata columns are fully supported in PowerApps. Source: Tips and Tricks for multiselect controls with advanced tagging options.


1

Yeah, you are on the right path. Use the "Required" property of the datacard and type in this: Assuming DataCardValue7 is your status field- If(DataCardValue7.Value="Red",true,false)


1

No, MS Forms does not have the capability, you can do some branching logic within the Form, but only based on previous questions within the same Form. I think you would be better off building a form in PowerApps. The interface to build is not nearly as quick and easy as MS Forms, but you have a lot more direct integration with other O365 data sources, ...


1

Users who are granted with Contribute, Read or lower permissions will not be able to “Add column”. The button will still be visible to the users, but they can only show or hide columns. If they try to save the modified view as a public view, they will get “Access Denied” error. You can check user permissions via https://{siteURL}/_layouts/15/user.aspx and ...


1

Modify the script as below: $User = "user@tenant.onmicrosoft.com" $Password = '*****' $url_sharepoint = "https://zheguo.sharepoint.com" $library = "doc1" $deleteFolders = "TestFolder" $source_folder = "C:\TestFolder" Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\ISAPI\Microsoft.SharePoint.Client.dll" Add-Type -...


1

The CSOM Method to delete the folder is DeleteObject(), for example: $targetFolder = $clientContext.Web.GetFolderByServerRelativeUrl($folderRelativeUrl); $targetFolder.DeleteObject(); $clientcontext.ExecuteQuery(); I would also say overall your script is doing things the hard way. You don't have to re-invent the PowerShell wheel. You should install the ...


1

The problem is that the "Members" group by default is granted the "Edit" permission level, and "Edit" is not what you think it is. The "Edit" permission level specifically grants users the rights to "Add, edit, and delete lists; view, add, update, and delete list items and documents. By default, this permission level is assigned to the Members group." ...


1

As @martin mentioned in comment, you can get sites through below url: your_host_name/_api/search/query?querytext='contentclass:STS_Site contentclass:STS_Web'


1

For me it worked in this syntax: {SearchBoxQuery} Path:{SiteCollection.URL}


1

Site permissions menu is available in modern experience, no matter what the site template is. You are possibly looking at the menu of a site that is not supported to connect Office 365 group, for example, publishing portal. The SharePoint groups (Owners, Members, Visitors) are automatically created in User Information list but will not be listed under Site ...


1

You can use column validation formula from list settings on your date time field, where you can restrict user from adding dates greater than or equal to tomorrow using below formula: =StartDate>=TODAY() Here, StartDate is column name. You will have to add this formula in column settings. Please below screenshot for the same:


1

// Starting with ClientContext, the constructor requires a URL to the // server running SharePoint. ClientContext context = new ClientContext("http://SiteUrl"); WebCreationInformation creation = new WebCreationInformation(); creation.Url = "web1"; creation.Title = "Hello web1"; Web newWeb = context.Web.Webs.Add(creation); // Retrieve the new web ...


1

It is supported in PowerApps. I’ve tested in a simple list with 5 single line of text fields, named A~E. For example, when I check the Checkbox control, the field A and B will be invisible and be replaced by fields C~E. Please see the steps below: Select Data Card for field A and switch to “Visible” under properties. Type If(Checkbox2.Value=false,true,...


1

I've faced a similar scenario myself; I used document sets (yet more info here) to create a document set and a handful of sub-folders. It sounds rather similar to what you are doing. In a nutshell: editing a List item then triggers a workflow to create a document set (and sub-folders) in a Document Library. Here's my post which makes use of Cameron Dwyer'...


1

My advice would be to forget the HTML files and just edit the ASPX itself. HTML page layouts were a bad idea, fraught with problems like this, and in Online there is no recourse when things don't go as expected.


1

Did you, by chance, try to open it using the Visio Designer? (DO NOT DO THIS FOR COMPLEX WORKFLOWS) I have done this for a complex workflow and it broke the Text-Based Designer. I'd also look to reinstall SharePoint Designer, as reinstalling fixed this for me.


1

Please check this other post here, they suggest installed Service Pack 1 to clear the issue. https://support.microsoft.com/en-gb/help/2817441/description-of-microsoft-sharepoint-designer-2013-service-pack-1-sp1


1

I'm posting an additional option for people that wish to use a no-code solution to this issue. If you wish to use managed metadata fields for other purposes, you'll need to convert/copy the values to a new field. Please read my post here which shows how to convert the values to a Single Line of Text field, by using a simple Sharepoint Designer workflow.


Only top voted, non community-wiki answers of a minimum length are eligible