1.  Navigate to https://www.onenote.com/staffnotebookedu and login to your tenant.
2. Select the "Create a staff notebook" tile.

Add the Staff Notebook to Microsoft Teams

1. Create a new Team in Microsoft Teams or use an existing one...doesn't matter.
2. Get the URL from the Staff Notebook you created above.
3. In Microsoft Teams, create a new tab in the Team you want to add the staff Notebook (Click the + sign in the respective Team channel)
4. Choose the "Website" tile

Share the vision

• Deployment driver - What got us here?
• Explain key business drivers and how it will impact them…for the better.
• Short/long term vision (phases of implementation and deployment)
• Start small and build momentum - don't build it in a day!

Identify relevant use cases

• What am I doing today?
  • Don't focus on moving 50,000 documents to SharePoint…focus on what activities am I doing today or in the last week.
  • This becomes you're immediate focus.
  • SharePoint SME's work with these groups initially to help them identify/train/explain how SharePoint will truly make it easier for them.
• Where are people storing documents now?
  • Start with the documents people use every day to collaborate.
  • If they are emailing documents for review…create a document library to collaborate.
  • Inventory the network drives to determine version history, folder security, nested folders (metadata).
• Employee self service
  • ID what resources people most often request or call/E-mail about and then develop content around that.
  • Site owners should constantly "mine" or review requests to keep the navigation current.
• What manual processes are done today?
  • What activities can be automated with workflow?
  • ID the inputs and desired state.
• How is Excel used?
  • Is a list more conducive to a spreadsheet?
  • Do users get locking messages all the time?
  • Are there a lot of complex formulas? If not then consider a list.
  • Contact lists or issue management stored in Excel and hard to manage?
• Project Management Maturity
  • All the activities of project management fit nicely into SharePoint.
  • Organize documents, tasks, issues, security etc in one site.
  • Use search to create dashboards.
• Key processes that can be automated?
  • Employee onboarding
  • Services requests
  • Any type of request and follow up process.
• What paper/electronic forms are being used that can become a list with a workflow?
  • Internal documents used as a template users fill out and return.
  • Paper forms that are printed and distributed.
  • Non-controlled forms (tax forms for example)…NOT a good SharePoint solution.
• How are people finding information?
  • Blanket E-mails…hey does anyone remember…or does any have the latest copy of XX.
  • Navigating a folder structure.
  • Using the search function in E-mail.
  • Desktop search appliances?
  • Give up and re-create?
• SharePoint becomes the system of record
  • As information has been identified and migrated to SharePoint…leadership needs to communicate that SharePoint is where you will go for this.
  • Remove permissions on file shares as content is migrated.
• Drive traffic to SharePoint
  • Encourage attaching links in E-mails versus documents.
  • Draft content on SharePoint and include links to the pages in E-mails or communications.
  • Adopt this into the organizations culture…"it's on SharePoint"…"submit your XXX on SharePoint" … "I put the document on SharePoint so we can collaborate on it".

Empower people

• Leadership sponsorship and support
  • Imperative to the success of any platform being adopted.
  • Must be driven from the top down.
  • Given the appropriate priority and resources to support.
• Get user buy in
  • What's in it for them?
  • Explain the use cases and practical ways it will impact their jobs/lives.
  • Must be empathetic to their situations - can't be "another IT initiative"
• Users have to participate
  • Identify those people that are technically more savvy and have usually been early adopters.
  • Embrace technology and the change it brings and displays a positive attitude towards it.
  • Provide them the necessary training to develop/enhance their skills.
  • Try to engage people who know their department/business process and can adapt to the functionality in SharePoint to make a real impact in their area.
• Form a SharePoint working group
  • Member include those business users identified above.
  • Combination of training and how are you using it sessions.
  • Promotes collaboration within the organization.
• Adoption will grow organically
  • Once people see how it will benefit them they will either jump on or ignore it. Focus on those that jump on and want to be your champions.
  • Have those champions work with the others in their department to foster/grow/train.
  • SharePoint SME's continually work with users to refine/enhance how they are using SharePoint.

Measure the success and expand

• Evaluate what is working and adjust
  • Keep content fresh and in front of people
  • Continually monitor the information architecture for a better search/navigation experience.
  • Identify what isn't working so well, analyze the outcome and make corrections.
• Expand to more groups
  • Continue to execute on the long term strategy.
  • Rinse and repeat on the approach.
• Showcase the successes
  • During organization meetings, reference how SharePoint has transformed a department does business and why.
  • Engage the communications people to help promote and use SharePoint. They generally send out the most customer facing information.
• Continually expand
  • Start to identify more complex use cases and solutions.
  • Review the information architecture for a relevant search experience.
• Measure and Govern
  • Police the governance plan to identify trends and user actions.
  • How many subsites are being created when a simple library can be used?
  • Review user traffic to sites and start to trend it so you know how to structure the navigation to accommodate these habits.
  • Review the 3 click rule (users shouldn't have to click more than 3 links to get where they need to) by analyzing usage patterns.
  • Expand/modify governance where necessary to accommodate newly released features/functionality.

1. The querytext parameter must use supported KQL query syntax.
2. The selectproperties querystring parameter must use managed properties in the SharePoint search schema.  You can have as many as you like but they must be managed properties.

JSON Response

PowerBI Data Set

Create a new parameter that will hold the REST request

1. From the Power BI desktop, the "Edit Queries" menu will bring you to a new screen where you can create and edit everything in this post.
2.  Create a new parameter from the Manage Parameters option.

3.     Create the new parameter and set the value to the REST query you want to execute.

Creating the base query

You will start with a blank query and put in the code necessary to transform the jSON response to a table that can be used.

1. In the blank query window you can then paste the following code.  This will retrieve the jSON response from the REST call to the SharePoint search API.

let

Source = Json.Document(Web.Contents(RESTQuery,[Headers=[Accept="application/json;odata=verbose"]])), d = Source[d], query = d[query], PrimaryQueryResult = query[PrimaryQueryResult], RelevantResults = PrimaryQueryResult[RelevantResults], Table = RelevantResults[Table], Rows = Table[Rows], results = Rows[results], #"Converted to Table" = Table.FromList(results, Splitter.SplitByNothing(), null, null, ExtraValues.Error), #"Expanded Column1" = Table.ExpandRecordColumn(#"Converted to Table", "Column1", {"Cells"}, {"Column1.Cells"}), #"Expanded Column1.Cells" = Table.ExpandRecordColumn(#"Expanded Column1", "Column1.Cells", {"results"}, {"Column1.Cells.results"}), #"Expanded Column1.Cells.results" = Table.ExpandListColumn(#"Expanded Column1.Cells", "Column1.Cells.results"), #"Expanded Column1.Cells.results1" = Table.ExpandRecordColumn(#"Expanded Column1.Cells.results", "Column1.Cells.results", {"__metadata", "Key", "Value"}, {"Column1.Cells.results.__metadata", "Column1.Cells.results.Key", "Column1.Cells.results.Value"}), #"Removed Other Columns" = Table.SelectColumns(#"Expanded Column1.Cells.results1",{"Column1.Cells.results.Key", "Column1.Cells.results.Value"}), #"Renamed Columns" = Table.RenameColumns(#"Removed Other Columns",{{"Column1.Cells.results.Key", "Key"}, {"Column1.Cells.results.Value", "Value"}})

in #"Renamed Columns"

2. When inserted the Advanced Editor should look like this:

3. What this is replicating are the steps that you can manually configure within Power BI.  Use this to get started and then you can modify the steps to fit your specific needs like renaming columns or splitting out values from a column.

KeyValueCount Query

1. Create a new Blank Query like you did above and paste in the following code:

let Source = SPSearch, #"Grouped Rows" = Table.Group(Source, {"Key"}, {{"Count", each Table.RowCount(_), type number}}), #"Removed Columns" = Table.RemoveColumns(#"Grouped Rows",{"Count"}), #"Counted Rows" = Table.RowCount(#"Removed Columns") in #"Counted Rows"

Transform the Search Results

1. Create a new Blank Query like you did above and paste in the following code:

let Source = SPSearch, #"Added Index" = Table.AddIndexColumn(Source, "Index", 0, 1), #"Inserted Integer-Division" = Table.AddColumn(#"Added Index", "Integer-Division", each Number.IntegerDivide([Index], KeyValue_Count)), #"Removed Columns" = Table.SelectColumns(#"Inserted Integer-Division",{"Key", "Value", "Integer-Division"}), #"Pivoted Column" = Table.Pivot(#"Removed Columns", List.Distinct(#"Removed Columns"[Key]), "Key", "Value"), #"Removed Other Columns" = Table.SelectColumns(#"Pivoted Column",{"Path", "Title", "Author", "RefinableString00"}) in #"Removed Other Columns"

2.  Note the "Removed Other Columns" line above.  This is where you'll see your managed properties from the SharePoint search API.  As you add managed properties to the selectproperties parameter of the REST call, they will automatically show up so you can use them in your reports and dashboards.

Display the Search Results

• The "Fields" pane on the right will display all of the managed properties returned by you're REST call to the Search API.
• Focus on using the "SearchResults" source to build you're dashboards.  The other "tables" are to assist in the ETL process.
• You'll have the full Power BI experience as other data sources with the ability to drill and refine you're results for maximum analysis of your SharePoint data.
• The full pbix file with all configurations can be downloaded from GitHub

• PowerBI Desktop - this is the desktop application that you'll need to gather, design and publish your dashboard solutions.
• PowerBI SKU to publish reports - even though PowerBI desktop is free, you'll need a license to publish this to PowerBI in O365 for others to interact with it.
• SharePoint list - For this post I'm using a standard SharePoint list that contains Contoso sales information.  Any list will do.

Getting the data from a list

• Fire up  PowerBI desktop and go Get Data -> More... -> Online Service -> SharePoint Online List:

• Provide the URL to your site (not the list)

• Choose the authentication method to connect to you're tenant:

• Once authenticated you can see the objects in the site.  Select the list you want to use as a data source.

Configure the PowerBI web part

• Navigate to PowerBI in O365 and get the URL of the report you want to use in the web part.

• Within your O365 site, create a new modern page and add the PowerBI web part (only available in the commercial cloud, not government cloud as of this publication date)

• Edit newly added web part and then paste in the URL copied from PowerBI.

• Publish the page and then view the report on your SharePoint page.

As you start to look through the pyramid to see where you might be or aspire to be, lets break down each slice of the pyramid.

• Configuration – often times this will be the introductory level of your SharePoint career and are able to effectively work with the businesses power user audience.  To do this you should be very familiar with not only what a content type is but the details on how to configure it and use it throughout your site collection.  This foundation will lead you to creating browser based workflows and using all the tools in the SharePoint browser experience to create solutions.
• Customization – Now that you have mastered the SharePoint browser experience and your information architecture (content types and list/library structure) has been configured,  you are ready to extend SharePoint.  Customizing the forms using InfoPath form Services,  SharePoint designer for list or libraries and PowerApps/Flow is probably your next step.  Within this level of expertise you start to really leverage SharePoint designer and some of the advanced web parts that SharePoint has to offer.
• Admin/Developer – This is where you typically reach a fork in the road.  It takes a unique person to really want to master the administration side of SharePoint (IE become a PowerShell guru and hang out in Central Administration more than anywhere else) and the development platform (IE Visual studio and the ability to create web parts and custom workflows).  This direction can come from personal interest or from a business need.
• Architect –  After years of working with everything in SharePoint and possessing the ability to configure just about anything using the SharePoint platform you have the experience and skills necessary to call yourself and architect.  Not only do you have a keen understanding of the features and functionality of SharePoint but you also recommend one approach over another because of performance implications, scalability or knowing the recommended thresholds of SharePoint.  Architects often possess experience in “supportive” technologies such as being a seasoned .NET developer, a system admin for the domain or a SQL Server DBA.  I’ve seen many times where this title is mis-interpreted as someone who understands the core features of SharePoint.  Yes this is a pre-requisite but you also need to have a solid understanding of how to get the requirements out of business users so you can apply the proper components or technologies to solve the problem.

Like all technologies that are complex, the ability to specialize in what interests you the most is what will drive not only personal satisfaction but your success with that chosen technology.  Hopefully this will position you for that succes

Issue

Resolution

1. You can run a Set-SPUser PowerShell command using the -SyncFromAD parameter but this will only update the name and E-mail in the User Information List.  If you want to update any other attributes from AD/User Profile this won't work.
2. Run a PowerShell script that will loop through all the users in the User Information List, which will the query the User Profile Service to get the updated attributes.  This will update as many attributes from the User Profile Service as you want, which is far better than the Set-SPUser method.

"The following query failed: <NameOfRESTQuery>"..."The underlying connection was closed: An unexpected error occurred on a receive"

1. Install the .NET Framework 4.7 - Starting with the .NET Framework 4.7, WCF allows you to configure TSL 1.1 or TLS 1.2 in addition to SSL 3.0 and TSL 1.0 as the default message security protocol.
2. Make necessary registry entries to support TLS 1.2
3. In the Web.Config file for the web application you intend to use TLS 1.2 on, make the following entry:

<runtime>

<AppContextSwitchOverrides value="Switch.System.ServiceModel.DisableUsingServicePointManagerSecurityProtocols=false;Switch.System.Net.DontEnableSchUseStrongCrypto=false" />

</runtime>

Adding the JavaScript

1. The first part of the script will override the Document Library hover panel footer template.

SP.SOD.executeFunc("callout.js", "Callout", function () { var itemCtx = {}; itemCtx.Templates = {}; itemCtx.BaseViewID = 'Callout'; //The template type of 101 is a document library itemCtx.ListTemplateType = 101; itemCtx.Templates.Footer = function (itemCtx) { //Override the footer of the hover card with your custom function. return CalloutRenderFooterTemplate(itemCtx, AddCustomAction, true); }; SPClientTemplates.TemplateManager.RegisterTemplateOverrides(itemCtx); });

2.  Now you can add your custom action:

function AddCustomAction (renderCtx, calloutActionMenu) { //Action you want to add to the footer calloutActionMenu.addAction (new CalloutAction ({ text: "View Properties", tooltip: 'View the properties of this document', onClickCallback: function() { //Determine the source of the list so you can navigate back to it. var listSource = _spPageContextInfo.serverRequestPath; //Make sure to append the ID to the URL so the item renders properly. window.location = renderCtx.displayFormUrl + "&ID=" + renderCtx.CurrentItem.ID + "&Source=" + listSource; } })) calloutActionMenu.addAction (new CalloutAction ({ text: "Edit Properties", tooltip: 'Edit the properties of this document', onClickCallback: function() { //Determine the source of the list so you can navigate back to it. var listSource = _spPageContextInfo.serverRequestPath; window.location = renderCtx.editFormUrl + "&ID=" + renderCtx.CurrentItem.ID + "&Source=" + listSource; } }));

3.  Finally display the default actions for the document library.

     //Display the default document library actions CalloutOnPostRenderTemplate(renderCtx, calloutActionMenu); }

SP.SOD.executeFunc("callout.js", "Callout", function () { var itemCtx = {}; itemCtx.Templates = {}; itemCtx.BaseViewID = 'Callout'; //The template type of 101 is a document library itemCtx.ListTemplateType = 101; itemCtx.Templates.Footer = function (itemCtx) { //Override the footer of the hover card with your custom function. return CalloutRenderFooterTemplate(itemCtx, AddCustomAction, true); }; SPClientTemplates.TemplateManager.RegisterTemplateOverrides(itemCtx); }); function AddCustomAction (renderCtx, calloutActionMenu) { //Action you want to add to the footer calloutActionMenu.addAction (new CalloutAction ({ text: "View Properties", tooltip: 'View the properties of this document', onClickCallback: function() { //Determine the source of the list so you can navigate back to it. var listSource = _spPageContextInfo.serverRequestPath; //Make sure to append the ID to the URL so the item renders properly. window.location = renderCtx.displayFormUrl + "&ID=" + renderCtx.CurrentItem.ID + "&Source=" + listSource; } })) calloutActionMenu.addAction (new CalloutAction ({ text: "Edit Properties", tooltip: 'Edit the properties of this document', onClickCallback: function() { //Determine the source of the list so you can navigate back to it. var listSource = _spPageContextInfo.serverRequestPath; window.location = renderCtx.editFormUrl + "&ID=" + renderCtx.CurrentItem.ID + "&Source=" + listSource; } })); //Display the default document library actions CalloutOnPostRenderTemplate(renderCtx, calloutActionMenu); }

References:

SharePoint 2010

1. Locate the ONET.XML file for the TeamSite (sts) template.  It will be located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\SiteTemplates\sts\xml
2. Open the file in Notepad.  There are 2 lines that need to be commented out to suppress the Calendar link.
3. Navigate to line ~87 and comment it out.  It should look like this:

SharePoint 2013

1. Navigate to the template folder:  C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\SiteTemplates\sts\xml and open the ONET.XML file in Notepad.
2. On Line ~73 modify the OnQuickLaunch attribute to be FALSE, which will suppress the "Documents" link on the quick launch:

Notes:

• Each of the ONET.XML files will be located in the respective SharePoint <hive> (IE 14 or 15) depending on the version.
• The C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\<VERSION>\TEMPLATE\SiteTemplates directory will hold all of the default site templates.  If you want to create your own, it's recommended to copy an existing one and modify where necessary.

• Select the proper web application and then General Settings -> Resource Throttling.

• Once in the Resource Throttling page, you can adjust the list view threshold for users and admins.

1.  The "IsThrottled" cmdlet is a Boolean that indicates if a list has been throttled.   Consider the following command:

$web = get-spweb http://sp $list = $web.lists["test"]

$list.IsThrottled

This will always return false for lists fewer than 5,000 items (or central admin settings if overridden)

2.  As soon as item 5001 is added then normal users will see the "this view cannot be displayed because it exceeds the list view threshold" message on the top of the list:

A couple things to note when the 5001 mark is met:

1. When an administrator accesses the list, they will still be bound to the list view threshold set in Central Administration. In our example it's 20,000 so they see the list items fine.

2.  When you re-run the PowerShell command above, now the Boolean value returned is true, indicating the list is now being throttled.

3.  To disable list throttling for the specified list, run the following PowerShell command:

$web = get-spweb http://sp $list = $web.lists["test"]

$list.EnableThrottling = $false $list.Update()

4.  Now when you run the $list.IsThrottled command, it will return false, indicating the list is no longer being throttled.  Users will now be able to see all the items in the list without the error message.

1. If a regular user goes into the All Events view and there are more than 5,000 items, they will see the list item threshold error.
2. If the same user goes into a specific calendar month that has more than 5,000 items, it will display just fine.

3.  If you click on the 5003 more items link it will expand and show all 5003 items (yes it does scroll forever!).

4.  When you page through the monthly view it does make a SQL call to the database.  I ran a SQL profile trace and it will use the beginning and ending day of that month to retrieve the results.  You do see some latency when going from page to page.

• Plan your indexing as part of the list/library planning.  If you try to create an index when the list is over the threshold, you will get a "Something went wrong" error.
• If you have grouping on your list, you still need to conform to the list view threshold requirements.

• Query Throttling and Indexing
• Manage Large Lists and libraries in SharePoint