Page 1 of 1

SalesQuote XML History: esp. expiry date

PostPosted: Wed May 01, 2019 10:45 pm
by pricerc
I'd like to import an expiry date with my quote, but it seems that the expiry date is *not* serialised when I export a quote, and putting a History tag and ExpiryDays didn't do anything.

Other things like opportunity status and notes would be good, too.

XML Output is:
Code: Select all
  <Histories>
    <History>
      <SalesQuoteHistoryID>9082c7cd3a1e492690c3</SalesQuoteHistoryID>
    </History>
  </Histories>

Re: SalesQuote XML History: esp. expiry date

PostPosted: Wed May 01, 2019 11:00 pm
by Mike.Sheen
Hi Ryan,

To save me some time, can you tell me the version of Jiwa you're experiencing this problem with?

Mike

Re: SalesQuote XML History: esp. expiry date

PostPosted: Thu May 02, 2019 8:00 am
by pricerc
7.2

Re: SalesQuote XML History: esp. expiry date

PostPosted: Thu May 02, 2019 1:25 pm
by pricerc
Actually, there are a few things lurking in there that aren't working as I would expect. TaxExemptionNo is another one that doesn't seem to be serialising.

We have quotes to import, and depending on the details, they may need to go out with different email templates. E.g., say 'Web Request', and 'Maintenance Renewal'.

For now, I can just use a bit of key data embedded in the OrderNo, but it's not a great place for what I need longer term.

So I was angling to use something like the 'Tax Exempt No' or the 'Opportunity Status Reason'.

I know I could use a custom field, but I was really hoping for something in the header, that I could put right at the top of the XML, next to 'OrderNo'.

In an ideal world, I'd like some kind of customisable categorisation field(s) in the quote header.

Re: SalesQuote XML History: esp. expiry date  Topic is solved

PostPosted: Thu Jun 20, 2019 11:26 am
by Mike.Sheen
Hi Ryan,

I've logged these issues as DEV-7592 - TaxExemptionNo is not serialised or deserialised when using the legacy XML and DEV-7596 - Sales Quote History fields are not serialised or deserialised

The DTO serialisation and deserialisation as used by the REST API suffered the same and issues for that are logged as DEV-7594 and DEV-7598

Mike