If you have a SharePoint .aspx page that has no master page content or containers and you want to include the SharePoint ECMA client object model libs, SharePoint is very particular about how you do that.
As we know, including the libraries is as simple as including the following line of markup:
<SharePoint:ScriptLink runat="server" ID="sl" Name="SP.js" OnDemand="false" Localizable="false" />
Note: the OnDemand attribute is set to false here to ensure that the script files are loaded immediately and so that we don't have to over-complicate with ExecuteOrDelayUntilScriptLoaded()
The key thing to remember with this piece of markup is that it MUST appear after the form element. So it will look a little like this:
<form id="form1" runat="server">
<SharePoint:ScriptLink runat="server" ID="sl" Name="SP.js" OnDemand="false" Localizable="false" />
I had originally tried to put this in the <head> ... </head> element and was left head-scratching as to why it failed to include the scripts.
04 July 2012
22 June 2012
[SharePoint] Wildcard Filter in Web Parts
SharePoint OOB filter web parts are quite useful. But sometimes (or often) we need a "little bit more" of them. One of the most wanted feature is how to filter a web part using only part of a word (wildcard search)
Luckily data view web part is always there to help us. Below you can find some good post about it:
"The Text Filter Web Part – Without Having To Filter Exact Text"
And if you still have doubts about SharePoint Designers 2010 exclusives web parts, you can give a look here:
"Working with Web Parts in SharePoint Designer 2010"
Luckily data view web part is always there to help us. Below you can find some good post about it:
"The Text Filter Web Part – Without Having To Filter Exact Text"
And if you still have doubts about SharePoint Designers 2010 exclusives web parts, you can give a look here:
"Working with Web Parts in SharePoint Designer 2010"
Subscribe to:
Posts (Atom)
Posts
