Client integrated QAS question

Hi Chuck,

Apologies for the delay in replying, my email rules had hidden your email!

We did manage to configure QAS to populate the DPID in the delivery_point field by editing settings in QAS Configuration Editor.  I can send you a screen shot of these settings if this would be helpful?

Note that while working on the location of the DPID data, we did find that we couldn’t use the Street3 field with integrated QAS.  QAS clears the Street3 field and there is no way to stop this behaviour, with the explanation from support being that Street3 is designed to be used by the Rapid Address technology, although we have never come across and address in the QAS/Australia Post database that contains 3 lines of Street data.

Cheers

Kim

From: Australia and New Zealand Tessitura Users [mailto:groups-aunz@tessituranetwork.com] On Behalf Of Charles (Chuck) Buchanan
Sent: Monday, 15 December 2014 3:28 PM
To: Kim Lee
Subject: Re: [Australia and New Zealand Tessitura Users] Client integrated QAS question

Hi Kim,

Did you find an answer to this question?

Where did you end up storing the DPID?  

Thanks,

Chuck

Hi,

I was wondering if there are any Australian licensees who have QAS integrated with the Tessitura v11 client via the Rapid Address button, and have found a way to get the DPID to populate a specific field, other than the street3 field? 

In v10 we are storing the DPID in delivery_point.  In v11, the DPID is landing in the street3 field and we’d like to change this to delivery_point, but as yet haven't figured out how to do so.

Thanks

Kim

Click here to report this email as spam.