New answers tagged

0

When you configure "Highlighted Content" with "this site" or "this site collection", you can set it sort by "Most viewed": However, if you choose a library, there is no "Most viewed" in Sort by option. Currently, there is no OOB modern web part to achieve your requirement, you need to develop a custom spfx web part to do that.


0

Seems you are looking for multi select cascading dropdowns, I found at code at below link, not tried though. But I think this should work with some tweaks. Ref link - https://social.msdn.microsoft.com/Forums/en-US/8d0ba6f6-8545-425e-8b4c-40e220b64f5a/cascade-dropdown-for-multi-select-lookup-fields?forum=sharepointdevelopment using // (Newform.aspx, ...


0

I figure out the solution, you need to use the following command in your console before create the solution. gulp bundle then create your solution again and reinstall it in app catalog.


1

Can't do with the "modern" Text Web Part as you cannot edit the HTML. You would need to add a NAME or ID attribute to an HTML tag. A recent discussion as to why here: How to use html code in modern UI A project to let you add HTML/JavaScript to modern pages (but it's a complex solution): https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/...


2

SharePoint web parts (modern and classic) are by default security trimmed, i.e. it won't show content to a user which are not allowed through permission.


1

I have just tested this and found the solution. First of all, you will have to remove the association with the hub site for the newly renamed sites. This can be done from the SharePoint online admin center. Then, associate the sites back with the same Hub site. This time the new title should show up.


1

Interesting use case, I am not sure if we are able to update via REST API but with CSOM you definitely can update Below Below is using Powershell CSOM, but same can be used in C# or Javascript object model. function Change-WebPart { #variables that needs to be set before starting the script $siteURL = "https://spfire.sharepoint.com" $userName =...


0

I think this is what you're looking for based on the comments above: var employees = []; function getADInfo(){ $.ajax({ url: "http://mes-server/CustomWebparts/DirectorySearch/roster.txt", method: 'GET', // dataType: 'json', cache: false, success: function(data) { console.log('success from getADInfo in JS'); // ...


0

You can hook into the client side rendering (CSR) system to register field validators to validate the value of the column before it is saved. There are some examples here and here and here, and here is an example pulled from some code I wrote just last week: var MyNamespace = MyNamespace || {}; MyNamespace.MyFieldValidator = function myFieldValidator () { ...


0

Promoted links are certainly supported on classic sites in O365. Can you not add the app? As an alternative, you can add a modern page to a publishing site. Of course, this would be changing out all the web parts, not just the one, but it would accomplish this specific goal. You may have to turn on the site pages feature first, as documented here.


0

Sample code snippet for your reference: .ascx: <SharePoint:ClientPeoplePicker runat="server" ID="PeoplePickerControlName" Required="true" ValidationEnabled="true" InitialHelpText="text" VisibleSuggestions="3" Rows="1" AllowMultipleEntities="true" CssClass="ms-long ms-spellcheck-true" /> ascx.cs: using System; using System.Web.UI; using System.Web....


1

I have a very convoluted way of doing this but due to restrictions in my office, this was the only way that would work for me. Should work for anyone else. Take your image and the correct size you want it. Put your image into the following site: https://image-map.weebly.com/# This will allow you the mark the specific areas that you want to become ...


1

Looks like there seems to be some issue going on with domain isolated webparts, for the time being would suggest that you not use that property. As mentioned in the comments, would suggest that you modify the config > package-solution.json file and set the isDomainIsolated value to false and then bundle, package and upload the solution and try again by ...


1

Try to call method getToken with 'https://graph.windows.net' to get the JWT token return tokenProvider.getToken('https://graph.windows.net') You can refer to these similar situation below: https://github.com/Azure-Samples/active-directory-angularjs-singlepageapp-dotnet-webapi/issues/19 https://github.com/SharePoint/sp-dev-docs/issues/3102


0

To access the site from another system you will need to add a DNS entry for "ABC" to point to the dev server.


0

Your DEV-Machine is not called abc. It's name is dev. So you cannot reach it with this name without workarounding configuration steps as already mentioned by others (HOSTS-File, DisableLoopbackCheck). Why do you call this machine with abc? Configure everything with dev and you won't need any workaround.


0

You may need to run the "Disable LoopBack check command" if your site is continuously asking for authentication . Please find the reference below :- https://social.technet.microsoft.com/wiki/contents/articles/37664.sharepoint-2013-disable-loopback-check.aspx Let me know in case of any concerns.


0

You haven't mentioned updating the host file on your dev machine. You need to go the sytem32\drivers\etc and update the host file with your 'abc' to machine itself. 127.0.0.1 abc


Top 50 recent answers are included