2/22/2015

Add JavaScript to Quick Launch in a 2010 Publishing Site

 

Note: The following will work in SharePoint 2010. For SharePoint 2013 you will need to use PowerShell. See here: http://techtrainingnotes.blogspot.com/2015/02/working-with-quick-launch-from.html

 

When you attempt to add a link that does not look like a URL to a SharePoint 2010 Publishing site you will get an error message like this one:

    image

The example above works perfectly with a non-Publishing site. What's different? The dialog box being used to do the edit.

The Work Around?

Cheat! Use the old editor for Quick Launch! (This will not work in SharePoint 2013.)

Go to your publishing site and then edit the URL in the browser's address bar so it points to _layouts/quiklnch.aspx

Something like http://yourServer/sites/yourPublishingSite/_layouts/quiklnch.asp

Click New Navigation Link or New Heading and add your JavaScript!

    image

And there you go!

For a SharePoint 2013 workaround using PowerShell see:

 

.

Working with Quick Launch from PowerShell

 

The following will work with both SharePoint 2010 and 2013. It will also work with SharePoint 2007 if you "manually" create the SPWeb object.

The basic steps to add a new link to Quick Launch:

  1. Get the SPWeb object for your site.
  2. Get the SPWeb.Navigation.QuickLaunch object.
  3. Create a new node .
  4. Add the new node to an existing node (like "Lists" or "Libraries") or the root of Quick Launch.
  5. Done… No need to call Update() on anything!

Note: This will work with publishing sites as long as you are not using Managed Metadata Navigation.

 

Get your web object and the QuickLaunch object:

$web = Get-SPWeb http://yourServer/sites/yourSite
$quicklaunch = $web.Navigation.QuickLaunch

You can explore your existing Quick Launch from here. Just type $quicklaunch and press enter to see your headings / top level nodes. Type $quicklaunch | where {$_.title -eq "Lists"} to see the links in one of the headings. You could even list all of the headings and their children with this one: $quicklaunch | select -ExpandProperty Children | Select {$_.Parent.Title}, {$_.Title}.

 

Create a new node object:

Each item added to Quick Launch is an SPNavigationNode object. It has three parameters: the text to display, the URL to the linked resource and $true if the link is external to SharePoint or $false if the link is internal to SharePoint. It appears that the $true/$false in the third parameter is used to see if the URL is validated as a real SharePoint URL or not. I could still add SharePoint links by leaving it as $true.

Example for a SharePoint link: (note the $false)

$navnode = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode("Get help!", "/sites/helpsite", $false)

Example for Bing or link external to SharePoint:

$navnode = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode("Bing", http://www.bing.com, $true)

Example for JavaScript:

$navnode = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode("Say Hello!", "javascript:alert('hello')", $true)

Example for JavaScript to open a new dialog box:
(Note the "`" in front of the "$" is needed because "$" means something special in PowerShell. (a variable follows))

$navnode = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode("Add a new task", "JavaScript:var options=SP.UI.`$create_DialogOptions();options.url='/sites/Publishing/Lists/Tasks/NewForm.aspx?RootFolder=&IsDlg=1';options.height = 400;void(SP.UI.ModalDialog.showModalDialog(options))", $true)

For more on JavaScript in Quick Launch see SharePoint: JavaScript in Quick Launch and Top Link Bar! and SharePoint: Opening a 2010 Dialog Box from Quick Launch.

 

Add the node to Quick Launch

To add the new node as a "heading" just add it to the Quick Launch object:

$quicklaunch.AddAsFirst($navnode)             or .AddAsLast

To add the new node as a child of a "heading" then use Where to find that heading:

$heading = $quicklaunch | where {$_.title -eq "Lists"}
$heading.Children.AddAsLast($navnode)

To add the new node after an existing node (i.e. not as First or Last) you will need to retrieve the existing node and then use the .Add method.

$existingLink = $heading.Children | where {$_.title -eq "Search the web with Bing"}

$navnode = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode("Search the web with Google", "http://www.google.com", $true)

$heading.Children.Add($navnode,$existingLink)

 

Delete a link?

Sure… Just retrieve the node and then call Delete.

$heading | Select -ExpandProperty Children | where { $_.Title -eq "Tasks" } | ForEach { $_.Delete() }

If you know that there's exactly one node that matches the Where test then you can shorten it to this:

($heading | Select -ExpandProperty Children | where { $_.Title -eq "Goog
le" }).Delete()

 

Bulk updates?

Sure… with extreme caution!  Danger! Will Robinson! Danger! Do the following at your own risk. No liability assumed, batteries not included!

Here's an example to add a Help link to every site in a site collection or to all site collections in the entire farm. (You way want to filter out the My Sites and the publishing sites!)

First confirm what you are about to change!

Get-SPSite http://sharepoint/sites/training | Get-SPWeb -Limit All | Select URL, Title
  
or
Get-SPSite -Limit All | Get-SPWeb -Limit All | Select URL, Title

Create the new link / node.

$navnode = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode("HELP!", "http://yourServer/sites/yourHelpSite", $true)

Now add it to every site in a site collection!

Get-SPSite http://sharepoint/sites/training | Get-SPWeb -Limit All | ForEach { $_.Navigation.QuickLaunch.AddAsFirst($navnode) }

or for all site collections in the farm:

Get-SPSite -Limit All | Get-SPWeb -Limit All | ForEach { $_.Navigation.QuickLaunch.AddAsFirst($navnode) }

 

And if you want to delete all of those helpful links?

Get-SPSite http://sharepoint/sites/training | Get-SPWeb -Limit All | ForEach { ($_.Navigation.QuickLaunch | where {$_.Title -eq "Help!"}).Delete()  }

 

What about a Publishing Site?

Publishing Sites use the "Navigation" editor for links and it does not permit "URLs" that don't begin with "http". This means that you cannot add JavaScript to a Quick Launch link using that editor. For SharePoint 2010 you can use the workaround here, or for 2010 and 2013 you can use the PowerShell above. (PowerShell to the rescue!) For more on JavaScript in Quick Launch see SharePoint: JavaScript in Quick Launch and Top Link Bar! and SharePoint: Opening a 2010 Dialog Box from Quick Launch.

The PowerShell above will work as long as in your Navigation settings you have not selected "Managed Navigation" or "same as parent".

image

 

References:

MSDN's article showing C# examples: (This is for 2010 but applies to 2007-2013.)

https://msdn.microsoft.com/en-us/library/office/ms427791(v=office.14).aspx

2/19/2015

Looking for __REQUESTDIGEST?

 

When the minimal Download feature is enabled, you cannot find the __REQUESTDIGEST by using Internet Explorer's View Source feature.

But there are two quick options:

  • You can find it using this JavaScript in the address bar:
    javascript:alert(document.getElementById("__REQUESTDIGEST").value)
  • Use the F12 Developer Tools. Click the DOM explorer then use the search box to search for __REQUESTDIGEST.

 

The Minimal Download feature?

What does the Minimal Download feature have to do with it? When enabled, this feature optimizes page downloads by only downloading what has changed since the last page load. Thing like Quick Launch, Top Link bar, Search, and the master page content in general, do not change when a user clicks links to lists and libraries. Cool feature? Some think not… If you are creating 2013 apps then you might want to take a look at this article: http://www.threewill.com/working-with-and-around-sharepoint-2013s-minimal-download-strategy/ and this one http://blogs.technet.com/b/jay/archive/2013/10/22/sp2013-new-feature-minimal-download-feature.aspx 

While I can't see huge differences with this feature enabled, I do find a lot of ugly URLs and issues with apps and with publishing sites. When doing development I do like to work with a URL like this:

https://yourServer/sites/yourSite/Shared%20Documents/Forms/AllItems.aspx

and not like this:

https://yourServer/sites/yourSite/_layouts/15/start.aspx#/Shared%20Documents/Forms/AllItems.aspx

 

image

 

.

2/15/2015

SharePoint Search Tip: Search for "title" where there is no "title"!

 

Title:somekeywords

image

You find the strangest things in SharePoint when you are looking for something else! I'm writing the labs for a new SharePoint 2013 Search Administration class and was looking for a list that did not support a search on "title:sometext". The list I first tested that did not have a "Title" column actually did work with a search for "title:". Huh? So I next tried the Links List as this one has always been a problem with the Content Query Web Part due to not having a "Title" column. I found that I could search Links with "title:sometext"! How?

 

Everything has a Title?

Almost…

Most SharePoint lists and libraries have a "Title" column. As "Title" is also an out of the box search Managed Property you can search these lists and libraries by using "title:airplane". If you browse around your sites though you will only find a few lists and libraries that have a "Title" column. For example: document libraries and announcements lists.

Out of the box lists and libraries that support a search on Title:

  • Some libraries and lists have an obvious Title column, so they are searchable on "Title". While libraries have a Title column, it is often not populated by users. Search will index the "Title" as the title field, when not blank, and otherwise index the "Name" column as "Title", so we can still search using "title:keyword".
  • Asset libraries have a "Title" column listed in the Library Properties page, but it's not listed on the Edit Properties page of videos, but we can still search using "title:keyword".
  • Custom lists where you have renamed the default title. Even after being renamed, it's still "Title" internally.
  • Lists with no displayed title column:
    • A Contacts list's "Last Name" column is internally named "Title". I.e. a search for title:smith works but a search for title:"mike smith" does not as "Mike" is not in the "Title/Last Name" column.
    • A Task list's "Task Name" column is internally named "Title".
    • A Discussion list's "Subject" column is internally named "Title".
    • A Categories list's "Category" column is internally named "Title".
    • A Content and Structure Reports list's "Report Title" column is internally named "Title".
    • A Links list has a hidden Title column that is auto-populated with the text from the "description" of the link.
    • A list created by importing an Excel file makes the first text column the clickable link column for the list. While the displayed name is whatever was imported, the internal name is "Title".

What does not have a Title?

  • Site Pages libraries.
  • Wiki libraries.
  • Visio Repository Site Process Diagrams libraries.
  • An external list (External Content Type) may not have a "Title" column.

 

Bottom line?

Almost every list is searchable using "title:somekeywords".

 

 

About the Links List

A Links list is special… or a least different. While many lists have a visible column with a name other than "Title" and an internal name of "Title", the List list is a bit different. A links list does not seem to have a end user accessible Title column, which is why its always been a pain with the Content Query Web Part. But… it does have a "Title" column, it's just hidden and Read Only. If you do a search using "title:", you will find links!  I guess its auto-populated and included just for searching. Here's the XML from the feature for the Links list:

image

 

.

2/10/2015

SharePoint 2013 List and Library Registration IDs, Feature IDs and ContentClass codes

 

Back in 2008 I created a list of SharePoint list and library registration IDs here. I updated it again in 2009, 2010 and 2014, and every time finding more list types to document. Well, I'm back again with yet another and larger list. The last update brought the list count up to 72 list types. This one ups the count to 107. While I was at it, I added the Feature that defines the list type, if the list type is typically searchable and the ContentClass codes that are used by search to find lists of that type. I will of course return to update this list again, and again, and again…

Column Notes:

  • Enum Name is from the Microsoft.SharePoint.SPListTemplateType enumeration. See the original article for C# and PowerShell examples of how to dump this list.
  • ID = the Registration ID, or list template ID. These are typically found in the Feature elements file that defines the list template. Example:
      <Elements …> <ListTemplate Name="announce" Type="104" …
  • Idx = Indexed by SharePoint search. If this is "No" or "Hidden" then you cannot use the contentclass code to search for these list types.
  • ContentClasses are used for searching for lists. A ContentClass search to find all Announcements lists might look like this:
       contentclass=STS_List_Announcements.
  • For each STS_List ContentClass there is a matching STS_ListItem to find all of the items in that type of list. For example, to find all announcements in SharePoint:
       contentclass=STS_ListItem_Announcements 
    or to find all of the announcements about the picnic:
       picnic contentclass=STS_List_Announcements
  • Refer to the original article for more details.

 

I will post an article in a few weeks that explores ContentClass and how it is used with search.

 

SharePoint 2013 List and Library Registration IDs, Feature IDs and ContentClass codes

 

Common Name

Enum Name

ID

Idx

ContentClass

Feature Name

Feature ID

 

InvalidType

-1

       
 

NoListTemplate

0

       

Custom List

GenericList

100

Y

STS_List

CustomList

00bfea71-de22-43b2-a848-c05709900100

Document Library

DocumentLibrary

101

Y

STS_List_DocumentLibrary

DocumentLibrary

00bfea71-e717-4e80-aa17-d0c71b360101

Survey List

Survey

102

Y

STS_List_Survey

SurveysList

00bfea71-eb8a-40b1-80c7-506be7590102

Links List

Links

103

Y

STS_List_Links

LinksList

00bfea71-2062-426c-90bf-714c59600103

Announcements List

Announcements

104

Y

STS_List_Announcements

AnnouncementsList

00bfea71-d1ce-42de-9c63-a44004ce0104

Contacts List

Contacts

105

Y

STS_List_Contacts

ContactsList

00bfea71-7e6d-4186-9ba8-c047ac750105

Events List

Events

106

Y

STS_List_Events

EventsList

00bfea71-ec85-4903-972d-ebe475780106

Tasks List

Tasks

107

Y

STS_List_Tasks

TasksList

00bfea71-a83e-497e-9ba0-7a5c597d0107

Discussion List

DiscussionBoard

108

Y

STS_List_DiscussionBoard

DiscussionsList

00bfea71-6a49-43fa-b535-d15c05500108

Picture Library

PictureLibrary

109

Y

STS_List_PictureLibrary

PictureLibrary

00bfea71-52d4-45b3-b544-b1c71b620109

 

DataSources

110

N?

 

DataSourceLibrary

00bfea71-f381-423d-b9d1-da7a54c50110

 

WebTemplateCatalog

111

N?

 

na

 
 

UserInformation

112

H

 

na

 

Web Part Gallery

WebPartCatalog

113

H

 

na

 

List Template Gallery

ListTemplateCatalog

114

H

 

na

 

Form Library (typically InfoPath forms)

XMLForm

115

Y

STS_List_XMLForm

XmlFormLibrary

00bfea71-1e1d-4562-b56a-f05371bb0115

Master Page Gallery

MasterPageCatalog

116

H

 

na

 

wfpub

NoCodeWorkflows

117

H

 

NoCodeWorkflowLibrary

00bfea71-f600-43f6-a895-40c0de7b0117

 

WorkflowProcess

118

N?

 

workflowProcessList

00bfea71-2d77-4a75-9fca-76516689e21a

Web Page Library

WebPageLibrary

119

Y

STS_List_WebPageLibrary

WebPageLibrary

00bfea71-c796-4402-9f2f-0eb9a6e71b18

 

CustomGrid

120

   

GridList

00bfea71-3a1d-41d3-a0ee-651d11570120

Solution Gallery

SolutionCatalog

121

H

     
 

NoCodePublic

122

N?

 

NoCodeWorkflowLibrary

00bfea71-f600-43f6-a895-40c0de7b0117

 

ThemeCatalog

123

H

     

Composed Looks

DesignCatalog

124

H

     

appdata

AppDataCatalog

125

H

     
 

DataConnectionLibrary

130

Y

STS_List_DataConnectionLibrary

DataConnectionLibrary

00bfea71-dbd7-4f72-b8cb-da7ac0440130

Preservation Hold Library

 

131

Y

STS_List_131

   
 

WorkflowHistory

140

H

 

WorkflowHistoryList

00bfea71-4ea5-48d4-a4ad-305cf7030140

Project Tasks List

GanttTasks

150

Y

STS_List_GanttTasks

GanttTasksList

00bfea71-513d-4ca0-96c2-6a47775c0119

 

HelpLibrary

151

   

HelpLibrary

071de60d-4b02-4076-b001-b456e93146fe

 

AccessRequest

160

   

AccessRequests

A0F12EE4-9B60-4ba4-81F6-75724F4CA973

Promoted Links

 

170

 

STS_List_170

PromotedLinksList

192EFA95-E50C-475e-87AB-361CEDE5DD7F

Tasks (2013 version)

TasksWithTimelineA ndHierarchy

171

Y

STS_List_TasksWith
TimelineAndHierarchy

HierarchyTasksList

f9ce21f8-f437-4f7e-8bc6-946378c850f0

 

MaintenanceLogs

175

   

MaintenanceLogs

8c6f9096-388d-4eed-96ff-698b3ec46fc4

Meeting Series

Meetings

200

H

 

na

 
 

Agenda

201

Y

STS_List_Agenda

na

 

Attendees

MeetingUser

202

Y

STS_List_MeetingUser

na

 

Decisions

Decision

204

Y

STS_List_Decision

na

 

Objectives

MeetingObjective

207

Y

STS_List_MeetingObjective

na

 

Text Box / Directions

TextBox

210

Y

STS_List_TextBox

na

 

Things To Bring

ThingsToBring

211

Y

STS_List_ThingsToBring

na

 
 

HomePageLibrary

212

   

na

 
 

Sites

300

   

SitesList

a311bf68-c990-4da3-89b3-88989a3d7721

Blog Posts/ Tabs List

Posts

301

Y

STS_List_Posts

BlogContent

0D1C50F7-0309-431c-ADFB-B777D5473A65

Blog Comments

Comments

302

Y

STS_List_Comments

BlogContent

0D1C50F7-0309-431c-ADFB-B777D5473A65

Blog Categories

Categories

303

Y

STS_List_Categories

BlogContent

0D1C50F7-0309-431c-ADFB-B777D5473A65

App Catalog

 

330

Y

STS_List_330

CorporateCatalog

0AC11793-9C2F-4CAC-8F22-33F93FAC18F2

Apps for Office

 

332

Y

STS_List_332

OfficeExtensionCatalog

61E874CD-3AC3-4531-8628-28C3ACB78279

App Requests

 

333

Y

STS_List_333

AppRequestsList

334DFC83-8655-48A1-B79D-68B7F6C63222

Restricted Permission List

 

397

   

AccSrvRestrictedList

A4D4EE2C-A6CB-4191-AB0A-21BB5BDE92FB

USysApplicationLog - Access

 

398

Y

STS_List_398

AccSrvUSysAppLog

28101B19-B896-44f4-9264-DB028F307A62

MSysASO - Access

 

399

Y

STS_List_399

AccSrvMSysAso

29EA7495-FCA1-4dc6-8AC1-500C247A036E

   

400

   

ScheduleList

636287a7-7f62-4a6e-9fcc-081f4672cbf8

Manage Resources

 

401

   

FCGroupsList

08386d3d-7cc0-486b-a730-3b4cfe1b5509

Resources - Group Work Site

Facility

402

Y

STS_List_Facility

FacilityList

58160a6b-4396-4d6e-867c-65381fb5fbc9

Whereabouts - Group Work Site

Whereabouts

403

Y

STS_List_Whereabouts

WhereaboutsList

9c2ef9dc-f733-432e-be1c-2e79957ea27b

Phone Call Memo - Group Work Site

CallTrack

404

Y

STS_List_CallTrack

CallTrackList

239650e3-ee0b-44a0-a22a-48292402b8d8

Circulations - Group Work Site

Circulation

405

Y

STS_List_Circulation

CirculationList

a568770a-50ba-4052-ab48-37d8029b3f47

Timecard (hidden) - publishing

Timecard

420

H

STS_List_TimeCard

TimeCardList

d5191a77-fa2d-4801-9baf-9f4205c9e9d2

 

Holidays

421

?

 

HolidaysList

9ad4c2d4-443b-4a94-8534-49a23f20ba3c

  .

425

?

 

WhatsNewList

d7670c9c-1c29-4f44-8691-584001968a74

StatusIndicatorList / KPIs

 

432

 

STS_List_432

BizAppsListTemplates

065c78be-5231-477e-a972-14177cc5b3c7

Report Library

 

433

 

STS_List_433

ReportListTemplate

2510D73F-7109-4ccc-8A1C-314894DEEB3A

   

434

       

Dashboard content

 

450

 

STS_List_450

PPSWorkspaceList

481333E1-A246-4d89-AFAB-D18C6FE344CE

Data Sources - Performance Point

 

460

 

STS_List_460

PPSDatasourceLib

5D220570-DF17-405e-B42D-994237D60EBF

   

470

 

1

BICenterDataconnectionsLib

26676156-91A0-49F7-87AA-37B1D5F0C4D0

Dashboards

 

480

 

STS_List_480

BICenterDashboardsLib

F979E4DC-1852-4F26-AB92-D1B2A190AFC9

Microsoft IME Dictionary List

IMEDic

499

N?

 

IMEDicList

1c6a572c-1b58-49ab-b5db-75caf50692e6

Categories - community site

 

500

Y

STS_List_500

CategoriesList

D32700C7-9EC5-45e6-9C89-EA703EFCA1DF

   

505

   

VisioProcessRepository

7E0AABEE-B92B-4368-8742-21AB16453D01

Visio Repository Site Process Diagrams

 

506

Y

STS_List_506

VisioProcessRepositoryUs

7E0AABEE-B92B-4368-8742-21AB16453D02

   

530

   

ContentFollowingList

A34E5458-8D20-4C0D-B137-E1390F5824A1

MicroBlogList (MicroFeed)

 

544

Y

STS_List_544

MySiteMicroBlog

EA23650B-0340-4708-B465-441A41C37AF7

SocialDataStoreList

 

550

   

SocialDataStore

FA8379C9-791A-4FB0-812E-D0CFCAC809C8

 

ExternalList

600

Y

 

ExternalList

00bfea71-9549-43f8-b978-e47e54a10600

My Site Documents

MySiteDocumentLibrary

700

 

STS_List_MySiteDocumentLibrary

MySiteDocumentLibrary

E9C0FF81-D821-4771-8B4C-246AA7E5E9EB

Product Catalog

 

751

 

STS_List_751

   

Pages Library

Pages

850

Y

STS_List_850

Publishing

22A9EF51-737B-4ff2-9346-694633FE4416

Asset Library

 

851

Y

STS_List_851

AssetLibrary

4BCCCD62-DCAF-46dc-A7D4-E38277EF33F4

Channel Settings

 

852

Y

STS_List_852

   

Hub Settings

 

853

Y

STS_List_853

   

Members - community site

 

880

Y

STS_List_880

MembershipList

947AFD14-0EA1-46c6-BE97-DEA1BF6F5BAE

for community site

 

925

   

AbuseReportsList

C6A92DBF-6441-4b8b-882F-8D97CB12C83A

Issue Tracking List

IssueTracking

1100

Y

STS_List_IssueTracking

IssuesList

00bfea71-5932-4f9c-ad71-1557e5751100

 

AdminTasks

1200

       
 

HealthRules

1220

       
 

HealthReports

1221

       

DraftAppsListTemplate

DeveloperSiteDraftApps

1230

Y

STS_LIST_DeveloperSite
DraftApps

Developer

E374875E-06B6-11E0-B0FA-57F5DFD72085

TransMgmtLib

Translation Management Library

1300

   

TransMgmtLib

29D85C25-170C-4df9-A641-12DB0B9D4130

xlatelist

Languages & Translations

1301

   

TransMgmtLib

29D85C25-170C-4df9-A641-12DB0B9D4130

   

1302

   

InPlaceRecords

DA2E115B-07E4-49d9-BB2C-35E93BB9FCA9

EDiscoverySources

 

1305

Y

STS_List_1305

EDiscoveryCaseResources

E8C02A2A-9010-4F98-AF88-6668D59F91A7

EDiscovery Source Instances

 

1306

H

 

EDiscoveryCaseResources

E8C02A2A-9010-4F98-AF88-6668D59F91A7

EDiscovery Source Groups / Sets

 

1307

Y

STS_List_1307

EDiscoveryCaseResources

E8C02A2A-9010-4F98-AF88-6668D59F91A7

EDiscovery Custodians

 

1308

Y

STS_List_1308

EDiscoveryCaseResources

E8C02A2A-9010-4F98-AF88-6668D59F91A7

Custom Lists / Queries

 

1309

Y

STS_List_1309

EDiscoveryCaseResources

E8C02A2A-9010-4F98-AF88-6668D59F91A7

EDiscovery Exports

 

1310

Y

STS_List_1310

EDiscoveryCaseResources

E8C02A2A-9010-4F98-AF88-6668D59F91A7

   

2000

   

PhonePNSubscriber

41E1D4BF-B1A2-47F7-AB80-D5D6CBBA3092

   

2001

   

ExternalSubscription

5B10D113-2D0D-43BD-A2FD-F8BC879F5ABD

Slide Library

 

2100

Y

STS_List_2100

SlideLibrary

0BE49FE9-9BC9-409d-ABF9-702753BD878

AccSrvAddApp / Access App

 

3100

   

AccSvcAddAccessApp

D2B9EC23-526B-42C5-87B6-852BD83E0364

wfsvc

 

4501

   

WorkflowServiceStore

2C63DF2B-CEAB-42c6-AEFF-B3968162D4B1

Acquisition History List

 

10099

 

STS_List_10099

   

Please don't just copy and paste this into another blog! The person who said "plagiarism is the sincerest form of flattery" did not do all of the work!. Feel free to reference this Tech Training Notes article as a source of this information.

.Additional Notes:

  • Not all lists are available in all sites. The available lists depend on the template and enabled features.
  • Not all of the lists can be created in SharePoint 2013, at least without using code or PowerShell. Many of these lists are “deprecated” and are only still supported for upgrades from older SharePoint versions.

 

.

SharePoint Search and Dates

 

I created a file on 2/7/2015. I searched SharePoint using "Write=2/7/2015" and could not find the file! When I found it by keywords, search said it was created on 2/7/2015.

    image

The library said it was created on 2/7/2015.

    image

When I searched using "Write=2/8/2015" I found it!

Turns out that search works in a different time zone! Here's the quote from this MSDN article:

"All date/time values must be specified according to the UTC (Coordinated Universal Time), also known as GMT (Greenwich Mean Time) time zone."

My testing is in Eastern Standard Time (EST), so GMT is currently 5 hours "in the future". When using GMT my file was created at 2/8/2015 12:50 AM.

 

Now try to explain that to all of your SharePoint users!

Smile

 

By the way… what time zone are you, or your users using? In my Office 365 subscription it's defaulting to PST when I create new site collections. I guess I should go check all of my other site collections and see I remembered to change to them all to EST when I created them!

image

 

.

Hide Documents from Delve

 

HideFromDelve!

Just stumbled on this buried in the middle of a Search Schema document.To hide documents from Delve you basically create a new Site Column named HideFromDelve as a Yes/No column, add it to your library and then set this column to Yes for everything you don't want to show up in Delve.

https://support.office.com/en-us/article/Manage-the-search-schema-in-SharePoint-Online-d4fab46d-ba41-4c03-9d4c-32b5b33198b6?ui=en-US&rs=en-US&ad=US#BKMK_HideFromDelveSteps

 

If you've not heard of Delve then start here: https://support.office.com/en-US/article/What-is-Office-Delve-1315665a-c6af-4409-a28d-49f8916878ca?ui=en-US&rs=en-US&ad=US

 

.

2/08/2015

Instant (almost) SharePoint 2013 Farm in Azure!

 

Microsoft Azure has had a pre-configured SharePoint 2013 image for quite a while, but you still had to create a SQL Server image to make it work and then run the SharePoint wizard to create the farm. Now they have a wizard approach to quickly create a ready to use three server basic farm or a nine server high-availability farm. Just click, click, click, wait a while and start playing with SharePoint! Just the thing for evaluations, demos and development.

The three server farm includes a SQL server, a DC server and a SharePoint server. The high-availability farm includes two DC servers, three SQL server servers, two application servers and two SharePoint web servers. (This one should drain your Azure budget! Remember to turn these off when not in use.)

Details on both configurations can be found here: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-sharepoint-farm-config-azure-preview/

Here's the steps to create your Azure SharePoint 2013 farm: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-sharepoint-farm-azure-preview/

 

A few observations:

  • SharePoint Version: 15.0.4571.1502  (Service Pack 1 (revised))
  • License: SharePoint Server Trial with Enterprise Client Access License
  • An initial web application and site collection have been created, but you will be asked to pick the template for the top level site on the first visit.
  • None of the services applications have been installed. User Profiles, Search, etc.
  • The VMs are available via Remote Desktop.
  • SharePoint is accessible from the web, so you can test from your local PC.
  • Outgoing and incoming email has not been configured.
  • Does not include Office Web Apps server.

 

Things you will need to do to have a complete SharePoint:

  • Configure the services
  • Configure email options
  • Add one more server VM for Office Web apps

 

Now all we need is a volunteer to create the PowerShell scripts to do the final work for us!

.

2/04/2015

SharePoint Dev Class 20488 in Two Weeks

 

I'll be presenting the 20488 Developing Microsoft SharePoint Server 2013 Core Solutions class in two weeks, actually a week and a half (time flies!). February 16th, 2015. We've set up this class for both local and remote students. Online students will be able to view the class and have remote access to the lab computers.

Just as a little incentive, when you register enter my code of "TTN50" and get a $50 discount on the class.

Details here: http://www.maxtrain.com/Classes/ClassInfo.aspx?Id=101693


MS-20488 Developing Microsoft SharePoint Server 2013 Core Solutions

In this 5 day instructor-led course, students learn core skills that are common to almost all SharePoint development activities. These include working with the server-side and client-side object models, developing and deploying features, solutions, and apps, managing identity and permissions, querying and updating list data, managing taxonomy, using workflow to manage business processes, and customizing the user interface.

At Course Completion

After completing this course, students will be able to:

  • Design and manage features and solutions.
  • Develop code for custom server-side components.
  • Manage and customize authentication and authorization.
  • Create custom sites and lists and manage the site lifecycle.
  • Explain the capabilities and design choices for SharePoint apps.
  • Use the client-side object model and the REST API.
  • Develop provider-hosted and auto-hosted SharePoint apps.
  • Distribute and deploy SharePoint apps.
  • Create custom workflows to automate business processes.
  • Use fields and content types to manage taxonomy.
  • Customize the appearance and behavior of user interface elements.
  • Customize navigation and site branding.

More details at http://www.maxtrain.com/Classes/ClassInfo.aspx?Id=101693

 

.

2/03/2015

A note to self-published book authors…

 

Actually a few notes…

 

I found two interesting SharePoint 2013 search books at Amazon and ordered them. I just received them… and I'm going to return both of them. This will be the first time I have ever returned a printed book!

 

Self-publishing is easy, fun and very rewarding. But…

Note 1: All printed technology books must have an index! Indexes are easy to create in Microsoft Word. You can either create a busy looking, but not too useful, index using the automatic features, or invest a couple hours and manually create a very useful one. In any case be forewarned, I do not buy technical books that do not have an index!

Note 2: Do not tell me in the book's intro that all of the content in the book is straight from your blog articles. Especially don't tell me that I could have gotten it all for free from the blog. (Boy, do I feel dumb paying for that book.) Don't just copy your blog articles and call it a book. Books that build on your blog articles can really be useful. Creating the book is your opportunity to expand on the topic and rewrite the quickly written text into nice complete articles. Fix up the screen captures. Fill in the gaps. Rewrite the hastefully written text. You know… create what you would have done in the blog if you had time to do it right the first time.

Note 3: Do not fill the pages with giant screen captures so there's an average of one screen capture and only one or two sentences per page. That works for a kid's picture book, but does not deliver much value as a technical book. In any case, please, please size and crop the screen captures so they are always readable and to the point.

Note 4: Pay somebody, anybody, to proofread the book. They don't have to know the technology. They just have to know some basic English and know enough to ask if all the code really should be underlined! If you want to really do it right, find someone who has heard of the Chicago Manual of Style, At a minimum buy yourself a copy of the Microsoft Manual of Style, and give a copy to your proofreader.

Note 5: Look at some of the tech books from the big publishers. I mean, open them, look at the details, note what is there and what is not. Note the use of "front matter". Note that page numbers go on the outside edges of pages, not in the gutter. Note the use of font size and the limited use of bold and italics.

 

</rant>

 

.

Note to spammers!

Spammers, don't waste your time... all posts are moderated. If your comment includes unrelated links, is advertising, or just pure spam, it will never be seen.