Sharepoint 2016 form with three PeoplePickers that each allow multiples within their respective field

I’m following this tutorial on how to setup a PeoplePicker and send the selected values via API. https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-in

My question revolves around a form that has 3 PeoplePickers on it. (Mgr, 2nd Mgr, and Assistant). The part of the tutorial that is confusing me is this section:

// Get the people picker object from the page.     var peoplePicker = this.SPClientPeoplePicker.SPClientPeoplePickerDict.peoplePickerDiv_TopSpan;   

Since I have three different people pickers, how do I keep track of which People Picker has which person selected? Do I define three different PeoplePickers in that section of code? Something like:

// Get the people picker object from the page.     var peoplePicker1 = this.SPClientPeoplePicker.SPClientPeoplePickerDict.peoplePickerDiv1_TopSpan;     var peoplePicker2 = this.SPClientPeoplePicker.SPClientPeoplePickerDict.peoplePickerDiv2_TopSpan;     var peoplePicker3 = this.SPClientPeoplePicker.SPClientPeoplePickerDict.peoplePickerDiv3_TopSpan; 

That just doesn’t seem right.. especially because of this code a few lines later…

// Get information about all users.     var users = peoplePicker.GetAllUserInfo();     var userInfo = '';     for (var i = 0; i < users.length; i++) {         var user = users[i];         for (var userProperty in user) {              userInfo += userProperty + ':  ' + user[userProperty] + '<br>';         }     }     $  ('#resolvedUsers').html(userInfo); 

I appreciate any help suggestions on how to tackle a form with three peoplepickers on it.

What version of Node.js can I use if I’m stuck on SPFx v.1.1.0 (SP 2016)?

I’m stuck on SharePoint 2016 for the time being, and I know that means I’m stuck using SPFx v.1.1.0.

However, I’m not sure what that means in terms of what version of Node.js to use.

I have some notes from a conference that say to use Node LTS v.8, but my notes are not clear on whether that means it must be exactly v.8, or at a minimum v.8.

I’m asking because I have a non-SharePoint project that is requiring Node LTS v.10, and I’m trying to figure out if I can just upgrade to Node v.10, or if I’ll have to install NVM so I can switch between 8 and 10 depending on what I’m working on.

Will SPFx v.1.1.0 work with Node LTS v.10?

SP 2010 Site Collection Migration to SP 2013 On-Prem to SP 2016 On-Prem to SP 2019 On-Prem | Moving from Classic to Modern Pages

I am new to an organization that is making the move from SP 2010 to SP 2013 to SP 2016 to SP 2019. These are all on-premise versions. The site collection has almost 3500 sites. There are lots of customizations – webparts that include more content editors that point to both jquery and html files.

For testing purposes, a team upgraded from SP 2010 to SP 2013. Nothing broke – yet. My concern is when they migrate to SP 2016, and the modern pages are turned on – content editor webpart does not exist in modern pages – SPFx rules. What happens on those pages where content editor webparts have been used for purposes of pointing to files? Is there a document for the best practices?

How to save the value of a Yes/No Checkbox via Sharepoint 2016 REST API onPrem?

How do you save checked/unchecked for sharepoint 2016 on-prem via the REST api? I have a couple input text boxes saving text, but I’m can’t save yes/no for cbAttending, I can’t seem to get the value when it’s checked. Appreciate any pointers.

<div class="form-group row">                 <div class="col-sm-12">                     <label class="form-check-label">                         <input type="checkbox" class="form-check-input" id="cbAttending" value="" />Attending?                     </label>                 </div>             </div>   <script> function addNew() {         var item = {             "__metadata": { "type": "SP.Data.NewListItem" },             "Title": $  ('#Field1').val(),             "Type": $  ('#Field2').val(),             "Attending": $  ('#cbAttending).val()               };  $  .ajax({     url: _spPageContextInfo.webAbsoluteUrl + "/_api/Web/lists/getbytitle('" + listName + "')/Items",             type: "POST",             contentType: "application/json;odata=verbose",             data: JSON.stringify(item),             headers: {                 "Accept": "application/json;odata=verbose",                 "X-RequestDigest": $  ("#__REQUESTDIGEST").val()             },             success: function (data) {                 console.log("item added...");                 },             error: function (data) {             }         });         return false;     } </script> 

Sharepoint 2016 internet explorer error – window.location.pathname is undefined

Hello i’m facing this problem in a sharepoint 2016 on-prem environment. i customize my masterpage (starting from the seattle one) adding some custom javascript such as following……………

<SharePoint:ScriptLink Language="javscript" Name="~sitecollection/Style Library/BMS/jquery.js" LoadAfterUI="true" Defer="true" runat="server" Localizable="false" />         <SharePoint:ScriptLink Language="javscript" Name="~sitecollection/Style Library/BMS/handlebars-v4.1.0.js" LoadAfterUI="true" Defer="true" runat="server" Localizable="false" />         <SharePoint:ScriptLink Language="javscript" Name="~sitecollection/Style Library/BMS/Bootstrap/bootstrap.min.js" LoadAfterUI="true" Defer="true" runat="server" Localizable="false" />         <SharePoint:ScriptLink Language="javscript" Name="~sitecollection/Style Library/BMS/Bootstrap/bootstrap-select.min.js" LoadAfterUI="true" Defer="true" runat="server" Localizable="false" />         <SharePoint:ScriptLink Language="javscript" Name="~sitecollection/Style Library/BMS/popper.min.js" runat="server" Localizable="false" />         <SharePoint:ScriptLink Language="javascript" Name="sp.runtime.js" runat="server" OnDemand="false" LoadAfterUI="true" Localizable="false" />         <SharePoint:ScriptLink Language="javascript" Name="SP.Taxonomy.js" runat="server" OnDemand="false" LoadAfterUI="true" Localizable="false" />         <SharePoint:ScriptLink Language="javascript" Name="~sitecollection/Style Library/BMS/Js/jquery.flagstrap.js" LoadAfterUI="true" Defer="true" runat="server" Localizable="false" />         <SharePoint:ScriptLink Language="javascript" Name="~sitecollection/Style Library/BMS/Js/initFlagstrap.js" LoadAfterUI="true" Defer="true" runat="server" Localizable="false" /> 

what happens is that sometimes the pages break using internet explorer (hiding the sharepoint above bar and no longer running javascripts in the page).

the first exception that i get using IE developer tools is :

SCRIPT5007: Unable to get property 'toLowerCase' of undefined or null reference in the file init.js (which is not custom). 

strangely if i type “window.location” in the console i get the object that i can expand and notice that window.location.pathname DOES have a value but if I type “window.location.pathname” in the console i get a variable = undefined error.

i’m getting crazy with that, anyone has any clue? thanks!!!

SP 2016 on -premises error: Sorry, we’re having trouble reaching the server

while sharing permission and in all sorts of people picker i’m getting this error “Sorry, we’re having trouble reaching the server” enter image description here on clicking Shared with i’m getting error “unexpected response data from serverenter image description here

i tried the following,

  • resetting IIS,
  • restarted the server
  • different user names
  • memory space is sufficinet

Please help me in fixing this error

Sharepoint 2016 Workflow – problems when sending email to multiple users

I have a flow that send e-mail to multiple users at once. No problem there… but suddenly, I had a problem with one email. That e-mail was invalid /incorrect, and sharepoint kept trying to send it over and over.. Since just one of the emails on the list was broken, all other users received emails several times, but SP was still trying to send it.. I had to stop the flow, cause they received more than 60 e-mails from Sharepoint.

I know that the ideal is NOT HAVING A BROKEN EMAIL there… but since it can happen again, I’m looking for alternatives.

The email is sent to a people picker field with multiple persons, separated with “;”.

If I build a dictionary with the users from this field, and run trough it sending the e-mail for each of then individualy, if it gets a broken e-mail will it stop? or it will keep trying to send the email and run though the dictionary again?

Any sugestion?

Ps: Sorry about my english.. it will get better, I promise =p

ps2: Is there some way to keep the workflow running when it gets an error?