Email Confirmation/Acknowledgement Questions

Hi David,  I have done this before.   I can post my template a little later in the day.  Basically what you do is call the ExecuteLocalProcedure web api method.  Then I take the dataset and update and add xml nodes to the OrderdataXML.  Once this is done it can be used in the transform. 

Regards,

Jon

David -

I'm not sure this is exactly what you are lookig for, but I've been successful pulling lineitem and sublineitem information using some of the example data structure that were included in the sample templates (particularly in the subscription section). In particular GetOrderDetailsInfoResults which you can pull both lineitem and sublineitems info. (Look at the sample template for an example)

Having said that, I'm only dabbling so far and haven't gotten very far, but I've been able to get some of that information!

Good luck,

Heather
Seattle Repertory Theatre 

Hi David,

Attached is our template and the xsl.  Please let me know if you have any issues opening the attachment. 

The part that pulls in addional information from tessitura  looks like:

 Tessitura.WebAPI.Tessitura tess = new Tessitura.WebAPI.Tessitura();
    string sessionkey = tess.GetNewSessionKey("");
    string lsal = "";
   
  
    DataSet ds = tess.ExecuteLocalProcedure(sessionkey, 1, "@ORDER_NO=" + OrderData.OrderNumber);

    for (int i = 0; i < ds.Tables[0].Rows.Count; ++i)
    {
        string superPkgNo = ds.Tables[0].Rows[i]["super_pkg_no"].ToString();
        string superPkgDesc = ds.Tables[0].Rows[i]["description"].ToString();
        string totPurAmt = ds.Tables[0].Rows[i]["tot_pur_amt"].ToString();
        string totRetAmt = ds.Tables[0].Rows[i]["tot_ret_amt"].ToString();
        string numPur = ds.Tables[0].Rows[i]["num_seats_pur"].ToString();
        string numRet = ds.Tables[0].Rows[i]["num_seats_ret"].ToString();
        string li_seq_no = ds.Tables[0].Rows[i]["li_seq_no"].ToString();

        XmlNode xm = OrderData.CartDocument.SelectSingleNode("//LineItem[li_seq_no=" + li_seq_no + "]");

        if (xm != null)
        {

            XmlElement xePkgNo = OrderData.CartDocument.CreateElement("super_pkg_no");
            xePkgNo.InnerText = superPkgNo;

            XmlElement xePkgDesc = OrderData.CartDocument.CreateElement("super_pkg_desc");
            xePkgDesc.InnerText = superPkgDesc;

            XmlElement xeTotPurAmt = OrderData.CartDocument.CreateElement("tot_pur_amt");
            xeTotPurAmt.InnerText = totPurAmt;

            XmlElement xeTotRetAmt = OrderData.CartDocument.CreateElement("tot_ret_amt");
            xeTotRetAmt.InnerText = totRetAmt;

            XmlElement xeNumPur = OrderData.CartDocument.CreateElement("num_seats_pur");
            xeNumPur.InnerText = numPur;
           
            XmlElement xeNumRet = OrderData.CartDocument.CreateElement("num_seats_ret");
            xeNumRet.InnerText = numRet;
           
            xm.AppendChild(xePkgDesc);
            xm.AppendChild(xePkgNo);
            xm.AppendChild(xeTotPurAmt);
            xm.AppendChild(xeTotRetAmt);
            xm.AppendChild(xeNumRet);
            xm.AppendChild(xeNumPur);

        }

This makes a wepapi  execute local procedure call , which pulls back extra information on the line item.  It then loops through the data set, search the order data xml for the matching node.  When it finds it , the additional is appended to the xml.  This is all done before calling the transform, so that it will be there when doing the xsl transform.

If you have any questions please let me know.

Jon 

Thanks Heather, Marty and Jon! It is all starting to make sense.