StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8239701
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-23T09:20:05.900
FavoriteCount
0
LastActivityDate
2011-11-23T09:20:05.900
LastEditDate
LastEditorUserId
0
OwnerUserId
7585
ParentId
8229317
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The XSLT 1.0 would make use of Muenchian Grouping. I think in this case, you are grouping twice. First you are grouping by InvestmentAccount elements, so you would need a key like so <pre><code><xsl:key name="Accounts" match="InvestmentAccount" use="concat(@Type, '|', @InvestmentStrategyId)" /> </code></pre> And then, you also need to group by Investment elements within the account. <pre><code><xsl:key name="Investments" match="Investment" use="concat(../@Type, '|', ../@InvestmentStrategyId, '|', @FundName)" /> </code></pre> Do note the use of the pipe in the concatenetion. This could be any character, but it must be one that does not feature in any of the attributes. To group by InvestmentAccount elements, you can then just match the first element in each group like the following: <pre><code><xsl:apply-templates select="InvestmentAccount[ generate-id() = generate-id(key('Accounts', concat(@Type, '|', @InvestmentStrategyId))[1])]" /> </code></pre> And once in the group, you can get all the Investment elements like so: <pre><code> <xsl:apply-templates select="//InvestmentAccount [@Type=current()/@Type] [@InvestmentStrategyId = current()/@InvestmentStrategyId]/Investment [generate-id() = generate-id(key('Investments', concat(../@Type, '|', ../@InvestmentStrategyId, '|', @FundName))[1])]" /> </code></pre> Here is the full XSLT (Do note I have assumed a root element called Investments <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" indent="yes"/> <xsl:key name="Accounts" match="InvestmentAccount" use="concat(@Type, '|', @InvestmentStrategyId)" /> <xsl:key name="Investments" match="Investment" use="concat(../@Type, '|', ../@InvestmentStrategyId, '|', @FundName)" /> <xsl:template match="/Investments"> <xsl:apply-templates select="InvestmentAccount[generate-id() = generate-id(key('Accounts', concat(@Type, '|', @InvestmentStrategyId))[1])]" /> </xsl:template> <xsl:template match="InvestmentAccount"> <xsl:copy> <xsl:copy-of select="@*" /> <xsl:apply-templates select="//InvestmentAccount[@Type=current()/@Type][@InvestmentStrategyId = current()/@InvestmentStrategyId]/Investment[generate-id() = generate-id(key('Investments', concat(../@Type, '|', ../@InvestmentStrategyId, '|', @FundName))[1])]" /> </xsl:copy> </xsl:template> <xsl:template match="Investment"> <xsl:copy> <xsl:copy-of select="@FundName" /> <xsl:attribute name="FundValue"><xsl:value-of select="format-number(sum(key('Investments', concat(../@Type, '|', ../@InvestmentStrategyId, '|', @FundName))/@FundValue), '0.00')" /></xsl:attribute> </xsl:copy> </xsl:template> <xsl:template match="@*|node()"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> </xsl:stylesheet> </code></pre> When applied to your sample XML (with a root element of Investments), the following is output: <pre><code><InvestmentAccount Id="Element01_Source3_Sequqence002" Type="Standard" InvestmentStrategyId="Employer" ParameterOverrideIds="AllocationRateOverride"> <Investment FundName="Fund032" FundValue="4754.82" /> <Investment FundName="Fund034" FundValue="4643.48" /> <Investment FundName="Fund035" FundValue="2509.46" /> <Investment FundName="Fund038" FundValue="7104.71" /> <Investment FundName="Fund042" FundValue="4244.08" /> </InvestmentAccount> <InvestmentAccount Id="Element01_Source4_Sequence003" Type="DWPRebate" InvestmentStrategyId="DSS" ParameterOverrideIds="DWPAllocationRateOverride"> <Investment FundName="Fund032" FundValue="1881.76" /> <Investment FundName="Fund034" FundValue="1584.18" /> <Investment FundName="Fund035" FundValue="872.99" /> <Investment FundName="Fund038" FundValue="2899.53" /> <Investment FundName="Fund042" FundValue="1762.62" /> </InvestmentAccount> <InvestmentAccount Id="Element01_Source2_Sequence001" Type="Standard" InvestmentStrategyId="Employee" ParameterOverrideIds="AllocationRateOverride"> <Investment FundName="Fund032" FundValue="7395.91" /> <Investment FundName="Fund034" FundValue="7222.72" /> <Investment FundName="Fund035" FundValue="3903.52" /> <Investment FundName="Fund038" FundValue="11051.32" /> <Investment FundName="Fund042" FundValue="6602.54" /> </InvestmentAccount> <InvestmentAccount Id="Element02_Source2_Sequence004" Type="TransferNonPR" InvestmentStrategyId="Employee" ParameterOverrideIds="AllocationRateOverride"> <Investment FundName="Fund032" FundValue="11056.71" /> <Investment FundName="Fund034" FundValue="12401.34" /> <Investment FundName="Fund035" FundValue="6634.86" /> <Investment FundName="Fund038" FundValue="16545.00" /> <Investment FundName="Fund042" FundValue="10036.26" /> <Investment FundName="fictiousextra" FundValue="1414.00" /> </InvestmentAccount> </code></pre> I wasn't sure how you wanted the attributes for the grouped InvestmentAccount element, but hopefully you can adjust that yourself.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSLT Grouping with addition/combination of sub elements
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTim C
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.