locked
Changes in AdCenterOrder? RRS feed

  • Question

  • Is it me or there was no announcement for a new property in AdCenterOrder?

    --> private boolean targetExists;

    This was raising axis deserialization errors for AdCenterOrder objects...
    Monday, December 11, 2006 8:55 AM

Answers

  • Hi,

    The CustomerManagement WSDL change (to include couponCode) was communicated in November. The change is reflected in the API topic at http://msdn2.microsoft.com/en-us/library/aa983133.aspx.

    The targetExists issue for AdCenterOrder is currently under review. We apologize for any inconvenience.

    Thank you.

    Walter Poupore - MSFT
    Microsoft adCenter Programming Writer.

     

    Tuesday, December 12, 2006 12:29 AM

All replies

  • I don't think it is just you, I didn't hear about it either.
    Monday, December 11, 2006 11:34 AM
  • Also FYI I have just downloaded all WSDLs again and there is a  change in CustomerManagement.asmx as well to CustomerSignUp
    Monday, December 11, 2006 12:26 PM
  • Ok, I downloaded all the wsdl this morning and built a new package for the API so I haven't checked if there were other changes.

    It does not seem to be a new version either! I am wondering what would happen if there is that kind of modification when the api developer (me for instance) is on vacation... our system will just stop doing its job!
    Monday, December 11, 2006 12:31 PM
  • Hi,

    The CustomerManagement WSDL change (to include couponCode) was communicated in November. The change is reflected in the API topic at http://msdn2.microsoft.com/en-us/library/aa983133.aspx.

    The targetExists issue for AdCenterOrder is currently under review. We apologize for any inconvenience.

    Thank you.

    Walter Poupore - MSFT
    Microsoft adCenter Programming Writer.

     

    Tuesday, December 12, 2006 12:29 AM
  • Just to expand a bit on this: the new property on AdCenterOrder was not intended to be public, but now that it's there we don't want to simply take it out and break people again. Perhaps we will do it in a future version, and communicate it properly.

    Sorry about that,

    Shai

    Wednesday, January 3, 2007 4:47 AM