Member Avatar for Anish Vatsya

I have one alias file which is acting as a wraper to XML.

<Alias name='Type'>
<Xpath>@subType</Xpath>
</Alias>

generally this return MEConsumed or MEResource. I want the behaviour that if @subType=MEConsumed then it should return CON and when @subType=MEResource then it should return "REF".
Help me with this .. i am very new to all this

Regards,
Anish

  • 2 Contributors
  • 5 Replies
  • 135 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by Anish Vatsya
Member Avatar for kaiLa 
if ()
    then expression 
  if (@subType=MEResource)
    then
  else expression

XPath has conditional statements, but XSLT might be easier to use since you only want to test two conditions. Then, you could use

<xsl:if test="{@subType=MEConsumed}">
  variableName="CON"
</xsl:if>
<xsl:if test="{@subType=MEResource}"
  variableName="REF"
</xsl>

Note, XSLT and XPath do not return statements like Java or other programming languages would. You'd want to set a variable and check it or set an attribute and check it.

Then again, their might be another way. Hope this helps even a little bit. :)

Member Avatar for Anish Vatsya

<Alias name='Type'>
<xsl:if test="{@subType=MEConsumed}">
variableName="CON"</xsl:if>
<xsl:if test="{@subType=MEResource}"
variableName="REF"</xsl>
</Alias>

on using this it throws an error::

The character '>' was expected. Error processing resource 'file://tc1016/New Folder/ME_FOLDER/Short-Term-Work/20_Anish/TcPu...

<xsl:if test="{@subType=MEConsumed}">
--------------^
Please guide

Member Avatar for kaiLa 
<Alias name='Type'>
<xsl:if test="{@subType=MEConsumed}">
    <xsl:variable name="testvar" value="CON" />
</xsl:if>
<xsl:if test="{@subType=MEResource}"[B]>[/B] <!--here is where > was missing-->
<xsl:variable name="testvar" value="REF" />
</xsl>
</Alias>

You need to create a variable
<xsl:variable name="ids" select="@ids" /> <!-- For instance -->
Initialize it, and then use that in place of "variableName/testVar." If you are calling a template, pass it using xsl:with-param and call it in the template as xsl:param. Here is a detailed description of xsl:param

Edited by kaiLa because: n/a
Member Avatar for Anish Vatsya

Yes that missing > i already placed. Still problem remains unchanged. I think the problem is related to introduce XSL syntax in XPATH.

<xsl:variable name="ids" select="@subType"/>
<html>
<body>
<xsl:call-template name="TY">
<xsl:with-param name="ids" />
</xsl:call-template>
</body>
</html>
</xsl:variable>

<xsl:template match="TY">
<xsl:param name="ids" />
<xsl:choose>
<xsl:when test="starts-with($ids,'MEConsumed')">
<xsl:value-of select="'CON'"/>
</xsl:when>
<xsl:when test="starts-with($ids,'MEResource')">
<xsl:value-of select="'REF'"/>
</xsl:when>

<xsl:otherwise>

<xsl:value-of select="'NONE'"/>


</xsl:otherwise>
</xsl:choose>
</xsl:template>


Please help me asap.

Member Avatar for Anish Vatsya

SEE ATTACHMENT.

Search for " <xsl:call-template name="TY"> "

<?xml version="1.0" encoding="UTF-8"?>

<!--
23-Nov-2005  arigapud                updated with inclass, form attributes
03-Mar-007   arigapud                Add ExportActivities
13-Jun-07    fitzgera                PR 5762630  Updated ExportActivities
$HISTORY$
-->

<!--
Using the alias file:
The alias file is to be used as a wrapper around plmxml file generated from TC to customize field names and extract relevant information from that plmxml file.
We can imagine the plmxml file to be the database and aliasFile as a query mechanism.
         
//A basic aliasFile would look like this - standard xml element. 
<?xml version="1.0" encoding="UTF-8"?>

//The version attribute on the Mappings element is used only during installation of TC (We check to see if the prior one has
 //the same version or not and only then import).
<Mappings version="2">
     //TraverseRoot element - should not be changed at all (unless the plmxml format for the starting element changes - unlikely.
     <TraverseRoot>/PLMXML/Header/@traverseRootRefs</TraverseRoot>
     //TransferModes section:A list of transfermodes - this is what is displayed in the UI - These must exist in Teamcenter - there is currently no check for that. 
    <TransferModes>
        <TransferMode name="tcm_export" description="Occurrences output"/>
        <TransferMode name="ExportGraphic" description="Output graphic file"/>
        <TransferMode name="ExportActivities" description="Export Activities only"/>
     </TransferModes>


      //Currently supported attributes on Alias element
       //The assetType attribute is treated as an enum - currently possible values
        // are 1 All(default), 2 Text, 4 3D Graphic, 8 Table, 16 2D Graphic 
        //toolTip - to show up in publish ui
        //qualifier - (1 - any, 2 - array, 4 - single)


     
     //Alias (top level) - These top level Alias elements (directly under Mappings element above) are what get displayed in the UI tree. 
     //And the children are picked up from there.
     //They must not have any Path,Xpath statements. Just Alias Child elements and any attributes like assetType,toolTip, qualifier.
      //   The assetType,toolTip,qualifier are looked at only at this level. This Alias element
      //    should list all the possible child alias elements.           
     <Alias name="Parent1" assetType="8" toolTip="product data" qualifier="2">
        <Alias name="Child1" default="use this value if you fail to evaluate"/>
        <Alias name="Child2"/>
    </Alias>
     <Alias name="Parent2" assetType="8" toolTip="product data" qualifier="2">
        <Alias name="Child11"/>
        <Alias name="Child21"/>
    </Alias>
    
    //ALIASALTERNATE: For each TopLevel AliasName there is one or more AliasAlternate elements. Each AliasAlternate element corresponds to 
    // what is the starting element in plmxml traversal. For example if you are standing on an ItemRevision in Navigator when you 
    // export the plmxml - the AliasAlternate elements that will be considered for processing
    //  are those with the first <Path>element whose primary is ItemRevision. Every Path element has 3 parts: Primary:Secondary:Relation. 
    //  The idea is to get to Secondary element from Primary element using the Relation. Relation is a pure XPath expression 
    // (typically just an xml attribute). The Primiary and Secondary elements can have xpath conditionals applied to them.
    //  Example: <Path>Occurrence:Occurrence[@subType='MEConsumed']:@occurrenceRefs</Path> means that, for this Primary Occurrence - 
    //  collect it's child Occurrences, only if they are of type
    //  MEConsumed (which is the subType attribute). Use Path elements to collect all the nodes in plmxml on which you want to perform an xpath 
    //  expression. A sequence of Path elements is just narrowing down the nodes on which to operate on.
     //    The only thing that will be contained in Top level AliasAlternate elements are the
     //    path subelements. These will be evaluated in sequence, to collect all the nodes on which the subsequent xpath will be applied. 
     //  The last path sub element in the Alias will yield the element(s) on which the xpaths will be evaluated.     
    <AliasAlternate name="Parent1">
      <Path>Primary|Primary1:secondary|secondary2:rel|rel2</Path>      //Here we are showing "oring" ability.
      //If the rel field does not end with @someRef (note that someRef could be attachmentRef or associatedAttachmentRefs and so on), it is combined 
      //with secondary condition and evaluated as one. Also, note that if you have namespace qualified elements - you would use ; as the token in the Path
      // element.
      <Alias name="Child1">
           <Xpath>@name</Xpath>
      </Alias>
      <AliasAlternate name="Child1">
           <Xpath>@name1</Xpath>
      </AliasAlternate>
    </AliasAlternate>

    // Each Path element can have a depth attribute and target attribute.
     default depth = "1..1" (immediate children)
            
      depth examples:
        depth="0..1" (0 and 1)
        depth="0..0" (only self)
        depth="0" (self and recurse)
        depth="1" (not self - but recurse on everything else).
        depth="2..4" (2,3,4)
        depth="leaf" (Collect only leaf nodes)
        
         If depth is specified - it will be active for each of the subsequent Path elements. To override this behavior - depth can be specified on the subsequent Path elements as appropriate.

      target attribute: This is to be used on a Path element when, grouping of results is desired based on the nodes resulting from that Path evaluation. No more than one target node is supported in a sequence of Path elements. The searching of AliasAlternate will stop if a Path element with target attribute is reached. The number of values returned will equal the number of target nodes (multiple values will be joined together if needed).

        
        
      //Xpath element can have these attributes - prefix, suffix - these are used to augment the output of the xpath expression.
      <Xpath prefix="THIS IS $PLMXML_DIR$" suffix=" Ending text">@name</Xpath>
       
        $PLMXML_DIR$ is a keyword - which will give you the physical location of the plmxml file directory. Can be used for getting the path for files referenced in plmxml.
        <Xpath prefix="$PLMXML_DIR$">@locationRef</Xpath>
        
        //If an xpath expression starts with a / - it is evaluated wrt the context node. If you want global context - you must specify absolute attribute on Xpath element.
        //Example:
        <Xpath absolute="true">/PLMXML/someelem/@attr</Xpath>
        
//        Another shortcut - if you want to join 2 values from the same base alias - you can use this
        <Xpath suffix="$BOM.Property&amp;bl_item_item_id$/$BOM.Property&amp;bl_rev_item_revision_id$">...</Xpath>
        Note that the element text is ... only. This would give you itemId/Rev - both of which are to be leaves at the same level.

      //Xpath text can have xpath 1.0 string functions. There is simple support of 
         //passing the id of context node: using the subst attribute.
        <Path depth='0..0'>ProcessOccurrence:*:*</Path>
        <Xpath absolute='1' subst='@id'>YourXpathExpression$@id$</Xpath>. Whereever
        //$@id$ appears - it will be replaced by the id of the ProcessOccurrence
          element. You can specify multiple substitutions - as subst='@id;@name' etc.


NOTE: To validate that the alias file is still a valid xml file (after making changes) - try to open it in internet explorer and make sure there are no errors.
     
</Mappings>

-->

<!--
  The DOCTYPE element below is used for ENTITY definitions - which reduce the number of lines to be copied.
-->

<!DOCTYPE Mappings [

       <!ENTITY FORM-MASTER-ATTR-DEF "
        <Alias name='project_id' default='cannot get project_id'/>
        <Alias name='previous_item_id' default='cannot get previous itemid'/>
        <Alias name='item_comment' default='cannot get comment'/>
        <Alias name='serial_number' default='cannot get serial_number'/>
        <Alias name='UserData1' default='cannot get user_data_1'/>
        <Alias name='UserData2' default='cannot get user_data_2'/>
        <Alias name='UserData3' default='cannot get user_data_3'/>  
        <Alias name='rev_project_id' default='cannot get project_id'/>
        <Alias name='rev_previous_item_id' default='cannot get previous itemid'/>
        <Alias name='rev_item_comment' default='cannot get comment'/>
        <Alias name='rev_serial_number' default='cannot get serial_number'/>
        <Alias name='rev_UserData1' default='cannot get user_data_1'/>
        <Alias name='rev_UserData2' default='cannot get user_data_2'/>
        <Alias name='rev_UserData3' default='cannot get user_data_3'/>           
      ">            
      
       <!-- inclass classification id alias defs-->
       <!ENTITY ICO-ATTR-DEF "
        <Alias name='RobotCapacity' default='cannot get classification_attributes' toolTip='Valid only for plmxml containing classification'/>
        <Alias name='RobotCapacity_unit' default='cannot get attributeId value pairs' toolTip='Valid only for plmxml containing classification'/>
       ">
    
     <!-- properties that you want to see on an occurrence. Entity definition is used to avoid lot of typing-->
     <!ENTITY OCC-ATTR-DEF "
        <Alias name='Part No' default='No ID'/>
        <Alias name='Description' default='No description'/>
        <Alias name='Name' default='no name'/>
        <Alias name='Rev' default='A'/>
        <Alias name='Transform' default='Identity'/>
        <Alias name='RevSubType' default='ItemRevision'/>
        <Alias name='LogicalID' default='Logical Identity'/>
        <Alias name='SequenceNumber' default='No find#'/>
        <Alias name='Quantity' default='1'/>
        <Alias name='ParentName' default='No parent'/>
        <Alias name='Type' default='No type'/>
        &FORM-MASTER-ATTR-DEF;
        &ICO-ATTR-DEF;
     ">
     <!ENTITY OCC-ATTR "
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.