The movie below shows an XML Fragment being used to populate a series of fields and an entire table.
The data sources is created with just two fields – one for the “Product ID” and one to contain the contents of the “ProductAttributes” node structure.
XML Example:
1 2 3 4 5 6 7 8 9 10 | <Product> <SKU id="1234"/> <ProductAttributes> <Attribute Name="Height" Value="100"/> <Attribute Name="Width" Value="50"/> <Attribute Name="Length" Value="200"/> <Attribute Name="Pack Size" Value="5"/> <Attribute Name="Voltage" Value="240"/> </ProductAttributes> </Product> |
Variations on the following “Computed Field” command are used to extract each attribute name into a set of field marker:
1 | EVALUATEXPATH(ProductAttributes,//Attribute[1]/@Name, '') |
The EVALUATEXPATH processes a simple XPath command on the contents of the “ProductAttributes” field. Here it’s used to retreive the ‘Name’ attribute of the first <Attribute> node. When the field content changes, Computed Fields are processed and updated just like normal fields. Computed fields commands can take content from any field in the record they are associated with.
General information on the XPath syntax can be found here.
The movie also shows tables being updated using a simple XSL stylesheet, which creates rows, columns and cells that are applied onto the table design. The example defines the following XSL:
1 2 3 4 5 6 7 8 9 10 11 12 | <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="/"> <table> <xsl:for-each select="//Attribute"> <tr> <td><xsl:value-of select="@Name"/></td> <td><xsl:value-of select="@Value"/></td> </tr> </xsl:for-each> </table> </xsl:template> </xsl:stylesheet> |
To keep the table content up-to-data, a formatting rule with the table should be setup and the field defined as a ‘Formatted Rule’ field type. When the field is inserted or updated, the Formatting Rule creates the table and re-creates the content.
