Archive for November, 2014

Next Tuesday, December 2nd 2014, I will be hosting a webinar together with Datapolis to talk about workflows, and more particularly SharePoint Designer Workflows. Here is the info:

Process automation is one of the most wanted benefits that SharePoint offers. In this session we will look at three must have workflows for SharePoint by using SharePoint Designer as well as a lot of useful tips and tricks that can be used in any SharePoint 2010 & SharePoint 2013 workflows.

 

Agenda

 

During this webinar you will learn how to:

– Improve business processes with workflow logic

– Select the workflow which meets your process requirements

– Choose between SharePoint Designer and other solutions depending on your needs

 

Duration

 

60 minutes

 

Speaker

Vlad is a SharePoint Consultant with more than 5 years in IT specializing in analyzing and deploying your perfect SharePoint infrastructure. He is currently working as a President and Senior Consultant at his own company: vNext Solutions. Vlad is currently the youngest SharePoint MVP in the world and is known in the community for his technical abilities and for founding the biggest and most active SharePoint Community that you can find at www.SharePoint-Community.net. Vlad also has his own blog at http://www.absolute-sharepoint.com and he often shares his knowledge by speaking at local conferences and community events.

 
 

Please note the event is at 10AM Eastern Time on the registration page of the webinar you can switch timezone to be able to see them in your timezone.

 

Register here: https://attendee.gotowebinar.com/register/1271680118121811714?source=spcommunity

No ratings yet.

Please rate this

Today I was at a client and we wanted to create a new Managed Property called “EntityName”. It looked simple, just create a new manage property, set your options, click OK and it’s done! However, we got this strange error:

internal problem connecting to or querying the database

“The settings could not be saved because of an internal error: There was an internal problem connecting to or querying the database.”

After reading the error message, my first reaction was checking if the SQL was up and I didn’t have any Access Denied errors in the Event Viewer. However, everything looked up. I then looked up in the ULS and found the following log:

SqlError: ‘Violation of PRIMARY KEY constraint ‘PK_MSSManagedProperties’. Cannot insert duplicate key in object ‘dbo.MSSManagedProperties’. The duplicate key value is (EntityName, 0).’ Source: ‘.Net SqlClient Data Provider’ Number: 2627 State: 1 Class: 14 Procedure: ‘proc_MSS_AddManagedPropertyEx’ LineNumber: 52 Server: SQLSERVER,1433′

SqlError: ‘The statement has been terminated.’ Source: ‘.Net SqlClient Data Provider’ Number: 3621 State: 0 Class: 0 Procedure: ‘proc_MSS_AddManagedPropertyEx’ LineNumber: 52 Server: SQLSERVER,1433′

According to the log, there is already a managed property called “EntityName” in Managed properties, however when I do a Search for it, it doesn’t show up!

I wanted to know more on the problem, so I went to SQL Database (PS: Microsoft doesn’t recommend you to do this!) and looked what’s inside the ‘dbo.MSSManagedProperties’ table. I then found something really interesting, there is a field called “Hidden”! And no surprise, my “EntityName” was in there:

So, to help you in the future, here are all the hidden Managed Properties in SharePoint 2013:

PID FriendlyName PID FriendlyName
0 All

2147418060

ows_taxId_SPLocationSite
2147418028 AnchorLink

2147418054

PHFlags
2147418033 BaseHref

69

PluggableSdid
2147418035 ChangeID

2147418042

PluggableSecurityBlob
2147418048 ChangeIDEnd

2147418089

PluggableSecurityTrimmerId
9 ContentExcludeFromSummaries

99

QIRExternal
2147418058 CrawlLogLevel

2147418057

RankPrecalBottom
2147418036 CrawlObjectID

2147418056

RankPrecalTop
2147418090 CrawlUrl

2147418019

RedirectedURL
2147418034 CRC

2147418018

Robots
2147450879 DefaultProperties

330

SameEnumDepthProps
2147418016 DirLink

2147418080

Scope
2147418021 DirLinkSecurityUpdate

2147418027

SecurityBlob
2147418020 DirLinkWithTime

2147418053

SecurityId
2147418026 EndAnchor

2147418031

SecurityProvider
2000000001 EntityName

2147418038

SiteContainer
2000000002 EntityNamespace

2147418088

SocialDistance
2147418022 FollowAll

2147418091

Summary Description
2147418023 FollowNone

70

TAUCCLICK0
12 IndexDocId

71

TAUCCLICK1
2147418037 IndexRare

72

TAUCCLICK2
183 InternalExpiresInDays

73

TAUCCLICK3
674 IsPartiallyProcessed

74

TAUCCLICK4
2147418039 LinkHRef

2147418049

TAUCCLICKNOTIFY
2147418040 LinkOfficeChild

2147418051

TAUCDISPLAYURL
2147418041 LinkOfficeChildList

2147418050

TAUCTITLE
2147418043 NonDocument

2147418046

TempAuthor
2147418024 NormalizedForwardURL

2147418062

TempLastModifiedTime
2147418025 NormalizedURL
68 NtSdid
2147418044 ows_MetadataFacetInfo
2147418045 ows_SPLocationInfo
2147418059 ows_taxId_SPLocationInfo
2147418061 ows_taxId_SPLocationList

So, to fix this problem, make sure you name your new Managed Property something that is not in the columns above!

Leave  a comment and don’t forget to like the Absolute SharePoint Blog Page on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

No ratings yet.

Please rate this

I was working at a client that was configuring Business Connectivity Services to bring data from an ERP into SharePoint. Of course, the main benefit of bringing it to SharePoint was being able to Search information using the powerful SharePoint 2013 Search Engine.

As you see in the following screenshot, I had 4 External Content Types from which I wanted to bring information in SharePoint. This guide assumes your profile pages for your External Content Types were already created!

First of all I created a new Content Source, setup all the options and run my full Crawl, I was able to search the data in SharePoint! Great!

However, the benefit of SharePoint Search is that you can heavily customize the search in order to bring results that really matter to the user. So, in my Enterprise Search Center, I wanted to add tabs that would only show me results from Projects or Clients. So, I created a new Search Page by clicking on the “Add Page” link in the Search Center and naming it “ClientResults”.

I then went into Site Settings > Search Settings and added a new “link”. I pointed it to “/search/Pages/ClientResults.aspx”

So Now, I did the same for “Projects” As well, so now when I go into my Search Center and click the arrow, I got the “Projects” and “Clients” choices!

But, whenever I Search, it doesn’t filter anything! It’s basically the same as “Everything”. We got to go change this! I will show the screenshots from the point of a SharePoint Administrator, however you can do this even if you don’t have access to the Central Administration! If you are a Power User, you can follow the tutorial from Site Settings > Search. We will use the “Schema” and “Result Sources” option.

Back to Central Administration > Service Applications
> Search Service Applications , on the bottom left, you will click on the “Search Schema“. And then Create a New Managed Property

Here are the Details I gave it:

 

 

Now, in the Mappings to crawled properties part, click on “Add a Mapping

In the “Business Data” Category, choose the “EntityName” crawled property and select OK.

 

Now, just click on the OK button and the managed property will be created!

 

Now that we got our managed property, we will need to do a full crawl of both the BCS and the SharePoint Content Sources! This will make sure that the data is crawled, as well as the search schema is updated!

After the full crawl is done, we will go in the Search Service Application > Result Sources and then click New Result Source.

After you fill the initial information, launch the “Query Builder

Create a Result Source for a BCS Entity

 

In the Query Builder, we will focus on the “Property Filter” part. First of all, click on the “Select Property” dropdown, and choose to “Show all managed properties”


Afterwards, reclick on the dropdown, select the BCSEntityName managed property we just created. The operation must be “Equals“. And then you will choose “Manual Value“. In the textbox right under, insert your database name, in my case it’s “client“. And then click on “Add property Filter“.

We will then click on the “Test Query” button. If everything is ok, you will see a bunch of your records and they are pointing to the good URL of your Profile Page!

Once that works , click on Ok to close the Query Builder, and then OK again to save your new Result Source!

Now, all we have to do is modify the Search Page to show us the right stuff! Navigate to your Search Center, Search for something random and go to the “Clients” Tab. Then, click on the settings wheel and click on “Edit Page”

Then, Edit the Search Results WebPart.

Click the “Change query” button.

 

In the Select a Query dropdown, choose the ClientBCS option! You can then customize it further in the Refiners & Sorting options, however we won’t go there in this tutorial. Click OK.

 

Afterwards, click OK on the “Edit WebPart” window.

Afterwards, check in the page and publish it! Now when you search in Clients, you should only find Client Names and nothing else! You are done!

Leave  a comment and don’t forget to like the Absolute SharePoint Blog Page on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

No ratings yet.

Please rate this

While configuring some Search Result Sources for a client, I had the following error when trying to build my query.

“The Search display templates are not present on this site collection. To add them, you need to activate the “Search Server Web Parts and Templates” feature on the Site Collection Features page.

Display Error: The display template had an error. You can correct it by fixing the template or by changing the display template used in either the Web Part properties or Result Types.

Template ‘~sitecollection/_Catalogs/masterpage/DisplayTemplates/System/Control_QueryBuilderPreview.js’ not found or has sytax errors. (Load Template: ) ”

Search Display Templates are not present on this Site Collection

After looking at what was missing, me and my colleague Joseph Henry Passineau found that in fact there was a feature missing on the Central Administration site collection. The feature is called Search WebParts. So, to fix the problem, simply run the following command in an elevated SharePoint Management Shell:

Enable-SPFeature SearchWebParts -url http://<central admin url>

Afterwards, re open the “build your query” page, and everything should work properly!

Leave  a comment and don’t forget to like the Absolute SharePoint Blog Page on Facebook and to follow me on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content.

5/5 (1)

Please rate this