Databases
StackOverflow2013
Postsdbo
PORemoving Duplicate Elements from my XML file by using an XSLT
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORemoving Duplicate Elements from my XML file by using an XSLT
    primarykey
    data
    text
    <p>Here is an example where I'd like to remove a duplicate entry if the ID is the same. I'm pulling hits from system 'A' and system 'B'. I want system 'A' to have precedence (i.e., if the ID is a duplicate, remove the element from system 'B'). Here's my example:</p> <p>I am getting this result:</p> <pre><code>&lt;HitList&gt; &lt;Hit System="A" ID="1"/&gt; &lt;Hit System="A" ID="2"/&gt; &lt;Hit System="A" ID="2"/&gt; &lt;Hit System="B" ID="1"/&gt; &lt;Hit System="B" ID="2"/&gt; &lt;Hit System="B" ID="3"/&gt; &lt;Hit System="B" ID="4"/&gt; &lt;/HitList&gt; I want this result (with the duplicates removed): &lt;HitList&gt; &lt;Hit System="A" ID="1"/&gt; &lt;Hit System="A" ID="2"/&gt; &lt;Hit System="B" ID="3"/&gt; &lt;Hit System="B" ID="4"/&gt; &lt;/HitList&gt; </code></pre> <p>Current Code:</p> <pre><code> &lt;xsl:template match="/RetrievePersonSearchDataRequest"&gt; &lt;HitList&gt; &lt;xsl:if test="string(RetrievePersonSearchDataRequest/SystemA/NamecheckResponse/@Status) = string(Succeeded)"&gt; &lt;xsl:for-each select="SystemA/NamecheckResponse/BATCH/ITEMLIST/ITEM/VISQST/NCHITLIST/NCHIT"&gt; &lt;Hit&gt; &lt;xsl:attribute name="System"&gt;&lt;xsl:text&gt;A&lt;/xsl:text&gt;&lt;/xsl:attribute&gt; &lt;xsl:attribute name="PersonID"&gt;&lt;xsl:value-of select="number( REFUSAL/@UID)"/&gt;&lt;/xsl:attribute&gt; &lt;/Hit&gt; &lt;/xsl:for-each&gt; &lt;/xsl:if&gt; &lt;xsl:if test="string(RetrievePersonSearchDataRequest/SystemB/NamecheckResponse/@Status) = string(Succeeded)"&gt; &lt;xsl:for-each select="SystemB/NamecheckResponse/PersonIDSearchResponse/personID"&gt; &lt;Hit&gt; &lt;xsl:attribute name="System"&gt;&lt;xsl:text&gt;B&lt;/xsl:text&gt;&lt;/xsl:attribute&gt; &lt;xsl:attribute name="PersonID"&gt;&lt;xsl:value-of select="number(.)"/&gt;&lt;/xsl:attribute&gt; &lt;/Hit&gt; &lt;/xsl:for-each&gt; &lt;/xsl:if&gt; &lt;/HitList&gt; &lt;/xsl:template&gt; </code></pre> <p></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjmac
    1. USjmac
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORemoving Duplicate Elements from my XML file by using an XSLT
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORemoving Duplicate Elements from my XML file by using an XSLT
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORemoving Duplicate Elements from my XML file by using an XSLT
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI am having trouble invoking any of the three proposed solutions. I currently am checking a 'Status' attribute for System 'A' and populating all of the Hits. Then, I am checking a different 'Status' attribute for System 'B' and populating all of the hits for this system. Where should I invoke the template? Should I use apply-templates or call-template?
      singulars
      1. PORemoving Duplicate Elements from my XML file by using an XSLT
      1. USjmac
    2. COI think that there is a misunderstanding here. The HitList with the multiples above isn't my input. My input XML has many layers and I'm grabbing the information from two separate places (in other words, two separate lists). The HitList above is my current output and the HitList with four items is my desired output. I will edit the question and show my XSLT that is producing the result above.
      singulars
      1. PORemoving Duplicate Elements from my XML file by using an XSLT
      1. USjmac
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload