XML Assistance

Hi all,

(Just also put this on the web forum, so apologies for the double post!)

I am in NO degree an XML expert and am trying to work with our web developers to get something on sale.  They are getting an error from our API that I am having trouble interpreting... Hoping anyone out there can lend a hand?

For most of the performances we are trying to get on sale, XML from the API looks like this:

Price diffgr:id="Price1" msdata:rowOrder="0">
<perf_no>13855</perf_no> 
<pkg_no>0</pkg_no>
<zone_no>625</zone_no>
<price_type>509</price_type>
<description>Orchestra Premium</description> 
<available>Y</available>

but with the problem performances, the last row, <available> is coming back as 'N' meaning that seating for the perf is not available on our website.

I can't figure out where this available indicator is in the client.  Any ideas?  I have got my Web MOS Active on all of my perfs and packages.  I have my Web Sales Price Type active in all perfs, connected to active Price Maps.  None of the zones in these Price Maps in Facility Manager are disabled.  The Perf Status in each Perf is on Sale and On Sale box is ticked, for good measure.  The Web MOS is connected to the Price Types it needs to be connected to in TX_MOS_PRICETYPE.  In Securities, the webuser has access to these MOS and Price Types.

I don't have Publish Client or Publish Web Dates set, but this is not a difference between those that are working.  Same goes for any custom Content keywords - there are none applied, to those perfs that are working OR those that are not working.

Frannie

Parents
  • Hi Frannie -

    This isn't a solution, but something I always try when trouble shooting - if you can log in to the client as the WebUser (or at least with the web user group) and see if you can pull and sell a ticket for that particular performance. 

    It *sounds* like you've checked all the normal culprits, but you never know.

    The other thing to watch is if you just changed things and your cache has possibly not refreshed or caught up (although this doesn't sound like the case either).

    Good luck!

    Heather

Reply
  • Hi Frannie -

    This isn't a solution, but something I always try when trouble shooting - if you can log in to the client as the WebUser (or at least with the web user group) and see if you can pull and sell a ticket for that particular performance. 

    It *sounds* like you've checked all the normal culprits, but you never know.

    The other thing to watch is if you just changed things and your cache has possibly not refreshed or caught up (although this doesn't sound like the case either).

    Good luck!

    Heather

Children