Step 1: Add the Content Editor Web Part to your NewForm.aspx

Open the NewForm.aspx page of your SharePoint list and add following parameters to the url: PageView=Shared&ToolPaneView=2, so your url looks like <…./Lists/yourlist>/NewForm.aspx?PageView=Shared&ToolPaneView=2.

You can now add the Content Editor Web Part to your NewForm.aspx page. Important is that you add the Content Editor Web Part below the already existing Web Part on your NewForm.aspx page, since we will add some JavaScript to the CEWP to manipulate the input fields. They should already by rendered before we execute our JavaScript.

Step 2: Add the JavaScript in your CEWP

Adding JavaScript in your CEWP can be done by chosing Edit>Modify Shared Web Part and clicking the Source Editor button to the right.

First we add a function to search the column to which we want to add the url to help our SharePoint users. This function I’ve already used in another post: How to set default values based on a query string and make those fields uneditable.

function getTagFromIdentifierAndTitle
(tagName,identifier,title){
  var len=identifier.length;
  var tags=document.getElementsByTagName(tagName);
  for(var i=0;i<tags.length;i++){
    var tempString=tags[i].id;
     if(tags[i].title==title && (identifier=="" ||
        tempString.indexOf(identifier)==
             tempString.length - len)){
      return tags[i];
    }
 }
 return null;
} 

Next we add an element with tag a to the Document object, to add a hyperlink text. This can be done with code as below:

var myLink = document.createElement('a');     
// The contacts list is located in the same site on the same level
// as the list for which the hyperlink is added to a column in 
// the NewForm.aspx page here
myLink.href = "/../../Lists/Contacts/NewForm.aspx"; 
// Open the hyperlink in a new browser window
myLink.target = "_blank"; 
// Text of the hyperlink
myLink.innerText = "Create New Contact   "; 

With the following code, we search the SharePoint column on the NewForm.aspx page whose field’s display name equals Contact. The type of the SharePoint column is Lookup. More information about this code can be found in a post on the Microsoft SharePoint Designer Team Blog: Using Javascript to Manipulate a List Form Field.

var theSelect=
  getTagFromIdentifierAndTitle("select","Lookup","Contact");     
// if theSelect is null, it means that the target list 
// has more than 20 items, and the Lookup is being 
//rendered with an input element   
if(theSelect==null)
{ 
  var theInput=getTagFromIdentifierAndTitle("input"
  ,"","Contact");    
  // Add the previously created hyperlink in front 
  //of the SharePoint column  
  theInput.insertAdjacentElement('beforeBegin',myLink); 
} 
else 
{  
  theSelect.insertAdjacentElement('beforeBegin',myLink); 
} 

Putting it all together, our added JavaScript in the CEWP should look like this:

<script language="JavaScript">

function getTagFromIdentifierAndTitle  
(tagName,identifier,title){     
  var len=identifier.length;   
  var tags=document.getElementsByTagName(tagName); 
  for(var i=0;i<tags.length;i++){     
    var tempString=tags[i].id; 
    if(tags[i].title==title && (identifier=="" ||     
       tempString.indexOf(identifier)== 
       tempString.length - len)){     
      return tags[i]; 
    }     
  } 
  return null;     
}

var myLink = document.createElement('a');     
// The contacts list is located in the same site on the same level  
// as the list for which the hyperlink is added to a column in 
// the NewForm.aspx page here 
myLink.href = "/../../Lists/Contacts/NewForm.aspx"; 
// Open the hyperlink in a new browser window     
myLink.target = "_blank";   
// Text of the hyperlink 
myLink.innerText = "Create New Contact   ";

var theSelect= 
  getTagFromIdentifierAndTitle("select","Lookup","Contact");     
// if theSelect is null, it means that the target list     
// has more than 20 items, and the Lookup is being 
//rendered with an input element     
if(theSelect==null) 
{     
  var theInput=getTagFromIdentifierAndTitle("input"   
  ,"","Contact");    
  // Add the previously created hyperlink in front 
  //of the SharePoint column     
  theInput.insertAdjacentElement('beforeBegin',myLink); 
}     
else   
{  
  theSelect.insertAdjacentElement('beforeBegin',myLink); 
} 
</script>

Remarks

• The great point about this modification is that our NewForm.aspx page isn’t unghosted. So adding new columns to our list in the future will become availalbe straight away in our NewForm.aspx page.



• You could put the code in an external JavaScript file, so you can run it on several pages. This way, you should also maintain your code on only one place. If you’ve put your code for example in an external file called HyperlinkNewForm.js and uploaded it in the Site Collection Documents library, you can replace the code in the CEWP added to your NewForm.aspx as follows:
  
  

  <script language="JavaScript" 
  src="http://<webapplurl>/SiteCollectionDocuments/
  HyperlinkNewForm.js"> 
  </script>

  
  

Problem Description: infolog asking to overwrite the existing file

Solution: Modify init method and modify RunOn property

To suppress this overwrite question, follow the two steps as below:

1. Step 1: Add following code to the init method of the report.

   
   public void init()
   {
       super();
   // suppress overwrite message
       element.printJobSettings().warnIfFileExists(false);
   …
   }

   
   


2. Step 2: Modify the RunOn property of the corresponding Menu Item so its value equals Client. In our example we’ll modify the Menu Output Item CustRevenue as in below screenshot.
   
   

   

   
   

Problem 1: The search service is currently offline

My search wasn’t functioning. Clicking on the Search Settings link in the Search section of my Shared Services Provider, I got following error: The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.

I restarted a couple of hundred times the search services, both in the SharePoint Central Administration, Operations sections as in the Services tool to start and stop Windows services under Administrative Tools on the Application Server . I relinked the indexer too couple of times, all without result.

Solution: Create a new Shared Services Provider

It all ended up by creating a new Shared Services Provider and change association of my restored Web Application to the newly created Shared Services Provider.

Off course, I deleted my restored Shared Services Provider too and had to reconfigure some settings in my newly created Shared Services Provider.

After this having done, my search service was functioning again in my new topology.

Problem 2: Alerts were not arriving

Alerts were not arriving anymore after the farm restore. After a while, I noticed the Immediate Alerts Timer Job Definition was missing (Central Administration > Operations > Timer Job Defintions).

Apparently, this Timer Job Definition was not restored upon a full farm restore…

Solution: Add the Immediate Alerts Timer Job Definition

Adding the Immediate Alerts Timer Job Definition could be done by running following instruction at the command prompt:

stsadm –o setproperty –pn job-immediate-alerts 
–pv “every 5 minutes between 0 and 59” –url <url>

And hey, alerts were arriving, and the Immediate Alerts Job appeared again in the Timer Job Definition list.

Problem 3: Other Timer Job Definitions missing

While I was looking for the missing Immediate Alerts Job missing, I remarked there were some other Jobs missing too after my farm restore. Following was the list of missing Timer Job Definitions:

• Change Log


• Database Statistics


• Dead Site Delete


• Disk Quota Warning


• Recycle Bin


• Usage Analysis

Solution: Running some other stsadm commands

I tried to use the same trick as for the Immediate Alerts Job, which worked for the Dead Site Delete and Usage Analysis Timer Job Definitions: they re-appeared. Unfortunately, I didn’t find how to let the others re-appear.

To fix the 2 Timer Job Definitions which I managed to let re-appear, run following commands at the command prompt:

stsadm –o setproperty –pn job-dead-site-delete
-pv “Daily at 00:00:00” –url <url>

stsadm –o setproperty –pn job-usage-analysis –pv
”Daily between 00:00:00 and 23:45:00” –url <url>