developers.valex.com.au - Valex Developer Documentation

We are making a backward-compatible change to where we parse Assessed Market Value (AMV) from LIXI messages.

Currently we parse the Assessed Market Value from:

//EstimatedValue[@EstimatedBasis="CertifiedValuation"]

However, this causes problems because we also parse contract price from the same place and only one EstimatedValue node is allowed by the LIXI schema:

//EstimatedValue[@EstimatedBasis="ContractPrice"]

We will be parsing the AMV from an additional location in the LIXI message:

//ValueComponent/MarketValueAsIfComplete[@Type="SinglePoint"]/@ValueCeiling

This will allow the Contract Price and AMV to be sent in the same response.

For Kerbside Reports where a midpoint and a Range (instead of SinglePoint) is provided, the legacy field (//EstimatedValue[@EstimatedBasis="CertifiedValuation"]) must be used for the midpoint. This means that if a midpoint is provided, then the same problem of not being able to provide the Contract Price will still be encountered. This is an edge case that we will ignore for now, but in the future we could add support for sending the midpoint in an alternative location if there is demand for it.

This will be a part of our next release (5 June 2011). This is now available on our testing site. Please give it a try and let us know if this new functionality causes any issues for you.