I often need to sign into SharePoint or another local server as a different user. An easy way to do this without logging out of your computer is to use the 'runas.exe' command. open a command prompt and enter the following command:
runas.exe /u:domain\username "C:\Program Files\Internet Explorer\iexplore.exe"
substitute domain\username with your account you want to login in with, I use a test account made specifically for these situations.
Friday, November 9, 2012
Monday, November 5, 2012
RANK function to create primary key for a Remedy View Form
To create Remedy View Form, you will need a database table or view that contains
a numeric primary key. Since your table or view might not have a column that
fits this requirement, you may need to dynamicall y create one in the building
of the view.
Use the RANK function to create an incrementing value and then cast it as a an integer:
CAST(RANK() OVER(ORDER BY TERM,CAMPUS,BUILDING,ROOM,CRS_PREFIX,CRS_NUMBER,CRS_SUFFIX) AS int) AS Record
Use the RANK function to create an incrementing value and then cast it as a an integer:
CAST(RANK() OVER(ORDER BY TERM,CAMPUS,BUILDING,ROOM,CRS_PREFIX,CRS_NUMBER,CRS_SUFFIX) AS int) AS Record
Thursday, October 18, 2012
AttachmentField control in SharePoint
The SharePoint
AttachmentsField is used to display attachments from an SP list
item.
<td align="center" id="att_{@ID}">
<xsl:if test="@Attachments='1'">
<SharePoint:AttachmentsField ID="att{@ID}" ControlMode="Display" ListId="{$ListID}" ItemId="{@ID}" FieldName="Attachments" visible="true" runat="server" />
</xsl:if>
</td>
The HTML that is rendered includes a table with a row for each attachment. The anchor tag look something like:
<a href="/student-affairs/athletics/athletics-w/basketball/Lists/Schedule/Attachments/11/statistics.html">20090312.6.html</a>
<td align="center" id="att_{@ID}">
<xsl:if test="@Attachments='1'">
<SharePoint:AttachmentsField ID="att{@ID}" ControlMode="Display" ListId="{$ListID}" ItemId="{@ID}" FieldName="Attachments" visible="true" runat="server" />
</xsl:if>
</td>
The HTML that is rendered includes a table with a row for each attachment. The anchor tag look something like:
<a href="/student-affairs/athletics/athletics-w/basketball/Lists/Schedule/Attachments/11/statistics.html">20090312.6.html</a>
Mod operator to control Table Rows in XSL
The Mod operator
returns the remainder left after division is performed. If you have a table and
you need to have a certain amounts of columns before another row is created, use
the mod operator.
The following example will create a new row after 3 columns are created.
<xsl:if test="position() mod 3 = 1">
<xsl:text disable-output-escaping="yes"><![CDATA[ <tr> ]]></xsl:text>
</xsl:if>
<td valign="top">
<img alt="" src="{@ImgURL}"/>
<xsl:call-template name="dvt_2" />
</td>
<xsl:if test="position() mod 3 = 3">
<xsl:text disable-output-escaping="yes"><![CDATA[ </tr> ]]></xsl:text>
</xsl:if>
The following example will create a new row after 3 columns are created.
<xsl:if test="position() mod 3 = 1">
<xsl:text disable-output-escaping="yes"><![CDATA[ <tr> ]]></xsl:text>
</xsl:if>
<td valign="top">
<img alt="" src="{@ImgURL}"/>
<xsl:call-template name="dvt_2" />
</td>
<xsl:if test="position() mod 3 = 3">
<xsl:text disable-output-escaping="yes"><![CDATA[ </tr> ]]></xsl:text>
</xsl:if>
Monday, September 24, 2012
Customizing the Summary Links with custom itemStyles.xslt
The
Summary Links control (PublishingWebControls: summarylinkfieldcontrol)
allows you to specify your own styles using the ItemXslLink property as shown
below.
<property name="HeaderXslLink" type="string">/Style Library/XSL Style Sheets/CustomHeader.xsl</property>
<property name="ItemXslLink" type="string">/Style Library/XSL Style Sheets/CustomItemStyle.xsl</property>
Save, add and upload your webpart. Your new header and styles will now be available.
<PublishingWebControls: summarylinkfieldcontrol
ItemXslLink="/Style Library/XSL Style Sheets/InsideHomeItemStyle. xsl"
.../>
In
SP Designer, you can copy an existing xsl file and rename it, you can then
update the file with your own styles and template names.
As
a demo of how this works, the following New Home page layout has two Summary
Link areas.
The
custom itemStyles.xsl file I created has only 2 styles to chose from;
insideHome1 & insideHome2. Both styles include a bullet icon in front of the
link but insideHome1 colors the link teal, insideHome2 colors the link
orange.
If you have a Links Webpart that you've added to a zone in your publishing page, you can export the webpart and modify the webpart file with the following xml:
<property name="HeaderXslLink" type="string">/Style Library/XSL Style Sheets/CustomHeader.xsl</property>
<property name="ItemXslLink" type="string">/Style Library/XSL Style Sheets/CustomItemStyle.xsl</property>
Save, add and upload your webpart. Your new header and styles will now be available.
Tuesday, September 18, 2012
Using the Previous function to supress Detail rows
When your query in Crystal does not return Distinct records, you may want to supress rows in the
Details section based upon the previous value of a field or fields. Add the
following code to the Supress code area in the Section Expert for the Details
section:
if (not onfirstrecord) then
previous({RDS_CLASS_VW.CLASS_CLASS_NBR})={RDS_CLASS_VW.CLASS_CLASS_NBR}
if (not onfirstrecord) then
previous({RDS_CLASS_VW.CLASS_CLASS_NBR})={RDS_CLASS_VW.CLASS_CLASS_NBR}
Wednesday, September 12, 2012
Using the IN Operator in a CAML Query
The In operator is used in an SQL query allows you to specify multiple values in a
WHERE clause. The CAML query language also uses the IN operator, in place of using multiple ORs, to return multiple values of a column.
<In><FieldRef Name='Col1'/>
<Values>
<Value Type='Text'>A</Value>
<Value Type='Text'>B</Value>
<Value Type='Text'>C</Value>
</Values>
</In>
WHERE clause. The CAML query language also uses the IN operator, in place of using multiple ORs, to return multiple values of a column.
<In><FieldRef Name='Col1'/>
<Values>
<Value Type='Text'>A</Value>
<Value Type='Text'>B</Value>
<Value Type='Text'>C</Value>
</Values>
</In>
Labels:
CAML,
SharePoint
Subscribe to:
Posts (Atom)