Sing Chan on general and SharePoint 2010 branding from Yaroslav Pentsarskyy on Vimeo.

Seems like a trivial task – all you need to do is to adjust XSL of the Search Core Results and remove or replace Author field, but there is a catch.

First, open your Search Core Results XSL:

I recomment you copy and paste the contents of the XSL editor into notepad (at least) and find the following section:

<!– Main body template. Sets the Results view (Relevance or date) options –>

this section denotes a start of the XSL responsible for rendering the body of the results. In here you will find all of the components that put together a search result. In my case I found and replaced the document author retrieval  implementation with the following:

<xsl:call-template name=”DisplayAuthors”>

<xsl:with-param name=”alias” select=”alias” />

</xsl:call-template>

After the XSL was saved, this worked well but I was still getting the actual CreatedBy in my search results. The created by information turned out to be coming from  the property called hithighlightedsummary

If you take a look at the definition of this property in your search service application: http://[central admin url]/_admin/search/listmanagedproperties.aspx

you will notice that hithighlightedsummary doesn`t have any of the crawled properties defined explicitly. In fact, this property is a dynamic summary that has a collection of highlighted word pieces that best describe the result and give user the text around the keywords they were searching. Among those calculated pieces of metadata we have CreatedBy and any other relevant metadata.

This means that no matter how much you customize your XSL – you will still receive some parts of the metadata as part of the hithighlightedsummary . One compromise is to remove this property from your XSL and replace it with a item description, body, or any other metadata that is relevant in your case.

Here is the template and selector that call hithighlightedsummary  from the XSL:

<xsl:when test=”hithighlightedsummary[. != '']“>

<xsl:call-template name=”HitHighlighting”>

<xsl:with-param name=”hh” select=”hithighlightedsummary” />

</xsl:call-template>

</xsl:when>

To create your new custom summary field you would define the managed property that will incorporate relevant crawled properties in here: http://[central admin url]/_admin/search/listmanagedproperties.aspx and then reference it in the template as shown above.

Don`t forget to include your newly created managed property in a list of fetched columns  within your Search Core Results:

Good luck!

]]>

Assuming you already have a rendering template ready or have just deplo0yed it – here is one quick way to rescue the day:

1. Open site in SharePoint Designer.

2. Click Lists and Libraries.

3. Click on the list you`d like to change the template on (Comments in my example)

4. Select the View of your interest, in my case I`ll be changing Display Form (ViewComments.aspx in case of Comments list)

5. The designer will load the view. Make sure you pick a split view to see visual and code of the form.

6. Click on the form as shown below, that way SharePoint Designer will show the piece of code representing the display form webpart.

7. In the “code” window find TemplateName in the highlighted section and find the “ListForm” property in that section and replace it with the rendering template that you have provisioned to the site.

That`s it, when done, just save the form and refresh the actual form page in your browser – the new form will be picked up right away.

Good luck!

Interview with Kurtis: SharePoint 2010 Insights from Visual Designer from Yaroslav Pentsarskyy on Vimeo.

Usually you’d use service job to create scheduled tasks within your portal such as batch business rules validation or alerts processing or really just about anything.

When you create your own Service Job it will be added to this list: http://[central admin url]/_admin/ServiceJobDefinitions.aspx

All Service Jobs have to be provisioned under web application. The best approach is to use SharePoint 2010 feature scoped to a Web Application and create an event receiver for the feature that will create an instance of a job based on the definition.

Here is how you’d go about creating a service job:

1. In your SharePoint solution create a new feature and scope it to the web application.

2. In the Template tree create a new folder where you will define any helpers that will be used to define your Service Job.

3. Create new feature receiver in the feature created in istep 1 and populate the following code in feature activated

SPWebApplication webApplication = (SPWebApplication)properties.Feature.Parent;
// remove any existing job definitions

foreach (SPJobDefinition jobDefinition in jobs)
            {
                if (jobDefinition.Name.StartsWith(”My Service Job Name“, StringComparison.InvariantCultureIgnoreCase))
                {
                    jobDefinition.Delete();
                }
            } 

            try
            {
                MyJobDefinition myJobDefinition = new MyJobDefinition(”"MyServiceJobId“”, webApplication);

            SPMinuteSchedule minuteSchedule = new SPMinuteSchedule();
            minuteSchedule.BeginSecond = 1;
            minuteSchedule.EndSecond = 59;
            minuteSchedule.Interval = 1000;
            myJobDefinition.Schedule = minuteSchedule;
            myJobDefinition.Update();
            }
            catch (Exception ex)
            {
                Microsoft.Office.Server.Diagnostics.PortalLog.DebugLogString(
                    Microsoft.Office.Server.Diagnostics.PortalLogLevel.Unexpected,
                    “Exception in Feature Activated occurred: {0} || {1}”,
                    ex.Message, ex.StackTrace);
                throw;
            }

4. Your feature deactivating method will have Service Job cleanup that will look something like this:

SPWebApplication webApplication = (SPWebApplication)properties.Feature.Parent;
// remove any existing job definitions

foreach (SPJobDefinition jobDefinition in jobs)
            {
                if (jobDefinition.Name.StartsWith(”My Service Job Name“, StringComparison.InvariantCultureIgnoreCase))
                {
                    jobDefinition.Delete();
                }
            } 

5.  Now you noticed we have MyJobDefinition  class from which we create a new job. This class will define what your job is actually doing. It has one method called Execute that will execute the job, you can either call another class that performs your operations if those are complex or you can define operations right in the Execute, here is how something like this will look like:

public class MyJobDefinition : SPJobDefinition
    {
        #region Constructors
        /// <summary>
        /// Default constructor is needed.
        /// </summary>
        public MyJobDefinition()
            : base()
        {
        }
        /// <param name=”jobName”></param>
        /// <param name=”webApplication”></param>
        public MyJobDefinition(string jobName, SPWebApplication webApplication)
            : base(jobName, webApplication, null, SPJobLockType.Job)
        {
            this.Title = “My Service Job Name“; //this will appear in Service Jobs list inside central admin
        }
        #endregion

        #region Methods

        /// <param name=”targetInstanceId”>ID of the content db that is processed by this job.</param>
        public override void Execute(Guid targetInstanceId)
        {
            try
            {

                SPWebApplication webApplication = this.Parent as SPWebApplication;
                // TODO: your scheduled code is here
            }
            catch (Exception ex)
            {
                Microsoft.Office.Server.Diagnostics.PortalLog.DebugLogString(
                    Microsoft.Office.Server.Diagnostics.PortalLogLevel.Unexpected,
                    “Exception in MyJobDefinition occurred: {0} || {1}”,
                    ex.Message, ex.StackTrace);
                throw;
            }
        }
        #endregion
    }

That’s it. Now this is basic implementation and you can improve various parts of your job such as pulling the schedule from configuration file rather than hardcoding it in the code etc. Good luck with your scheduled tasks!