Products

Solutions

Resources

Partners

Community

About

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsXMLXMLis it possible to use a calculated field in the WHERE clause in XSLT?is it possible to use a calculated field in the WHERE clause in XSLT?
Previous
 
Next
New Post
9/28/2009 5:21 PM
 

i have the biggest pain in the butt with my data because it is missing a unit cost. i have to calculate the unit cost on the fly and there may or may not be a sale price for any unit. i can get it alright. but when i want to select the next batch of data, i need the records to be bigger than the previous batch's maximum unit cost.

my code looks like this portion:

CASE pv.SalePrice
  WHEN 0 THEN pv.Price / ABS(pv.SKUSuffix)
ELSE 
   pv.SalePrice / ABS(pv.SKUSuffix)
END AS UnitCost   <-------my calculated unit cost

               FROM {databaseOwner}{objectQualifier}aspdnsf_Product p
                    join {databaseOwner}{objectQualifier}aspdnsf_ProductManufacturer pm on p.ProductID = pm.ProductID 
                    join {databaseOwner}{objectQualifier}aspdnsf_Manufacturer m on pm.ManufacturerID = m.ManufacturerID 
                    join {databaseOwner}{objectQualifier}aspdnsf_ProductCategory pc on p.ProductID = pc.ProductID 
                    join {databaseOwner}{objectQualifier}aspdnsf_Category c on pc.CategoryID = c.CategoryID 
                    join {databaseOwner}{objectQualifier}aspdnsf_productvariant pv on p.ProductID = pv.ProductID 
                    join {databaseOwner}{objectQualifier}aspdnsf_SalesPrompt sp on p.SalesPromptID = sp.SalesPromptID
                    left join {databaseOwner}{objectQualifier}aspdnsf_ExtendedPrice e on pv.VariantID=e.VariantID and e.CustomerLevelID=@CustomerLevelID
                WHERE p.ProductID <> @ProductID  

                    and UnitCost > @PreviousMaximumUnitCost <-----this is what I'd LIKE to do but it errors out
                    and pv.SalePrice > 0
                    and p.Deleted = 0
                    and pv.Deleted = 0
                    and p.Published = 1
                    and pv.Published = 1
                    and p.PortalID = @PortalID
                    and pv.VariantID in(select min(VariantID) from {databaseOwner}{objectQualifier}aspdnsf_productvariant where ProductID = p.ProductID and published=1 and deleted=0 and p.published=1 and p.deleted=0)
                ORDER BY UnitCost asc
 

anyone know how i can do this?

 

 
New Post
9/29/2009 5:51 PM
 

I don't understand the relation between your question and the posted SQL.

You can set variables in XSLT, and you can use them also in xpath statements to filter your nodes.

<xsl:variable name="aname" select="1" />

<xsl:foreach select = "yournodes[position()>@aname]">....

I suggest to read an instruction to XSLT like http://www.w3schools.com/xsl/default.asp

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsXMLXMLis it possible to use a calculated field in the WHERE clause in XSLT?is it possible to use a calculated field in the WHERE clause in XSLT?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out