The Setup Properties listed below are available for use. Click on a link to go directly to that section.
Insert Edit Configuration XML
Store Content Before Analysis
Used to add a column to the data collected from the external XML sources. This is useful if you want to set a default value for a column if the initial column is null, like a currency field.
Go to http://msdn2.microsoft.com/en-us/library/system.data.datacolumn.expression(VS.71).aspx for more information.
Example:
<AddColumn>
<Column>
<ColumnName>ZeroOfGroup1</ColumnName>
<ColumnType>System.Int32</ColumnType>
<Expression>IsNull(1*[Group Value0], 0)</Expression>
</Column>
</AddColumn>
The name of the column you want to add.
The type of column you want to add. Please see Convert XML/ColumnType for available options.
The expression used to store data within the column.
Use this property to force the web part to renew data collection during any operation within the grid. This is useful when on a 64bit server and you have more than one grid on the page.
Use this property convert fields collected from the external XML from a String to a different type.
Note: This procedure will occur after the Mapping XSL has been applied.
Example:
<Convert>
<Column>
<ColumnName>Start Date</ColumnName>
<ColumnType>System.DateTime</ColumnType>
</Column>
<Column> </Column>
</Convert>
The name of the column you want to convert.
The System Type you would like to convert the column to.
Options:
System.Boolean
System.Byte
System.Char
System.DateTime
System.Decimal
System.Double
System.Int16
System.Int32
System.Int64
System.SByte
System.Single
System.String
System.TimeSpan
System.UInt16
System.UInt32
System.UInt64
TableName (Optional) String
The name of the table which contains the column to convert. The TableName comes from the Table node used in the XML. For instance if your xml looks like <Data><Title>Hello</Title></Data><Data><Title>World</Title></Data> the name of your table is Data.
Allows you to create a relationship between data elements inside of your data source. This is used when representing parent-child items inside the grid.
Example:
<Relations>
<Relation>
<Parent>
<Name>Parent1</Name>
<Keys>
<Key>ParentID</Key>
</Keys>
</Parent>
<Child>
<Name>Child1</Name>
<Keys>
<Key>ChildID</Key>
</Keys>
</Child>
</Relation>
<Relation> </Relation>
</Relations>
The URL to use when deleting an item using the inline edit ability of the grid.
Use this property if there is content that should be deleted from the finished data table. Each element stored will look for a matching Column Name and value and delete that row from the data table.
Example:
<DeleteExtraData>
<Delete>
<ColumnName>Group Value</ColumnName>
<ColumnValue/>
</Delete>
<Delete> </Delete>
</DeleteExtraData>
The name of the column to search within.
The value to search for. For null, enter nothing.
The URL to use when editing an item using the inline edit ability of the grid.
The URL to use when creating a new item using the inline edit ability of the grid.
The URL location of the configuration file which will be used to manage the inline edit ability of the grid.
Used to specify the XSL to be used to format the content collected before it is displayed within the web part. For instance, if you wish to display an item as a link, you would use XSL to create a link to an item from the data collected.
This property also supports the Common Use Variables stated at the beginning of this help topic.
Options:
"[file]="
o Use this option to specify a URL to an XSL Stylesheet Template
o Example: [file]=<%SiteURL%>/Connections/TasksXSL.xml
<xsl:stylesheet> </xsl:stylesheet>
o Use this option to specify the XSL Stylesheet XML directly within the property
o Example:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<Data>
<xsl:for-each select="NewDataSet/Table1">
<Item>
<Title><xsl:value-of select="Title" /></Title>
</Item>
</xsl:for-each>
</Data>
</xsl:template>
</xsl:stylesheet>
Use this property to pass page parameters onto the page specified in the URL to XML property. This supports the Common Use Variables stated at the beginning of this help topic. You must encode the < and > symbol when using the parameters (e.g., < < and > >).
Example:
<PassThrough>
<Pass>
<PTType>get</PTType>
<PTRequest>SearchString</PTRequest>
<PTName>SearchString</PTName>
<PTDefault>[Me]</PTDefault>
</Pass>
</PassThrough>
The default text that will be sent to the page from which data is being requested, if the parameter is not passed into the page.
The name of the parameter that is to be passed onto the page from which data is being requested.
The name of the parameter that is being received by the page.
Controls the type of pass through. Use "post" to store the parameters in the header of the request or use "get" to store them in the URL.
Options:
post
get
Stores XML that defines the layout of the grid, such as grouping, filters, sorting, and column arrangement.
Use this property to store content into the data table before analysis. The data that will be collected can either be created from an Expression, it can be come from a get/post request from another page, or it can be a static value. The difference between this and the Add Column XML property is that this process occurs before any analysis is completed, versus after.
Example:
<ExtraPreData>
<Data>
<ColumnName>Event Start</ColumnName>
<ColumnType>System.String</ColumnType>
<PageRequest>StartDateNew</PageRequest>
</Data>
<Data> </Data>
</ExtraPreData>
The name of the column to add.
The type of column to add. Please see Convert XML/ColumnType for available options.
The static value to store within the property.
The expression used to store data within the column.
The Page Request variable to collect when this page is called. This can come from either a get request or a post request.
The URL to the data source that the grid will reference for data to display. This property also supports the Common Use Variables stated at the beginning of this help topic.
Default: empty
Example:
http://domain.com/GridDataSources/Tasks
<%SiteURL%>/GridDataSources/Tasks