StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20090644
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-11-20T08:17:56.463
FavoriteCount
0
LastActivityDate
2013-11-20T23:48:28.293
LastEditDate
2013-11-20T23:48:28.293
LastEditorUserId
7585
OwnerUserId
7585
ParentId
20084257
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
It looks like for each "model", you are trying to find the cheapest Item for that model. To get the SupplierCode for the current Price element you are on, you could just do this... <pre><code><xsl:template match="Price"> <xsl:if test="position() = 1"> <xsl:value-of select="."/> <xsl:value-of select="../SupplierCode" /> </xsl:if> </xsl:template> </code></pre> Where <code>..</code> is used to get the parent of the current node. Alternatively, what you could do is instead of selecting the Price elements with you template, select the Item element, ordered by Price <pre><code><xsl:apply-templates select="current-group()"> <xsl:sort select="Price" data-type="number" order="ascending"/> </xsl:apply-templates> </code></pre> Then, you can have a template matching the Item element, and in this you be easily able to access the Price and Code <pre><code><xsl:template match="Item"> <xsl:if test="position() = 1"> <xsl:value-of select="Price" /> <xsl:value-of select="Code" /> </xsl:if> </xsl:template> </code></pre> EDIT: In answer to your comment, if you only wanted the SupplierCode for the Item with the lowest price, you would change the template matching the Item element to output just the supplier code, and then wrap the xsl:apply-templates in a variable. Try this XSLT <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output omit-xml-declaration="yes" indent="yes" /> <xsl:template match="/*"> <xsl:for-each-group select="Items/Item" group-by="@model"> <xsl:variable name="SupplierCode"> <xsl:apply-templates select="current-group()"> <xsl:sort select="Price" data-type="number" order="ascending"/> </xsl:apply-templates> </xsl:variable> <xsl:value-of select="$SupplierCode" /> </xsl:for-each-group> </xsl:template> <xsl:template match="Item"> <xsl:if test="position() = 1"> <xsl:value-of select="SupplierCode"/> </xsl:if> </xsl:template> </xsl:stylesheet> </code></pre> Actually, there is another way of doing this. You could make use of the min operator in XSLT 2.0 <pre><code> <xsl:value-of select="current-group()[number(Price)=min(current-group()/Price)]/SupplierCode" /> </code></pre> This wouldn't necessarily be as efficient as the previous method though because you are effectively checking the "current-group()" twice. First to get the minimum value, and then again to find the Item in the current-group with the lowest price.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGet Element Value according to another element in XSL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTim C
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. POGet Element Value according to another element in XSL
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COI'm sorry I may be asking something stupid but how would I retrieve the Supplier Code by itself then?
 singulars
 PostPostId
 PO
 UserUserId
 USEnzero
2. COI've expanded my answer to hopefully make it clearer.
 singulars
 PostPostId
 PO
 UserUserId
 USTim C

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.