Selective recipients from a database

127 views
Skip to first unread message

MichaelB

unread,
Jan 11, 2010, 12:46:14 PM1/11/10
to XMPie Interest Group
Does anyone know of a way to only pull a certain number of recipients
based on the data?
I have one database for a company. In that database is a field with
different branch numbers.

I would like the customer to be able to pick a newsletter template on
uStore and fill out the variable data content, then from a drop down
choose a branch number that will get that mailing. Then at check out
finalizing only those recipients from that field would be generated
for print.

Thanks in advance

Bill

unread,
Jan 12, 2010, 11:13:38 AM1/12/10
to XMPie Interest Group
As far as I know, Plan Filters do not (yet) support Plan Variables.
You did not mention, if the Data Source used by your customers will be
uploaded (Excel, Access or XML), or uProduce-based. Can you specify?
If uploaded, I think an additional restriction applies: Plan Filters
cannot be applied to uStore uploaded Data Sources.

I would do the following:
* I would define a Dial Variable in uPlan;
* I would define a fake Text ADOR, which would call the QLingo "Skip"
function, should the |->[branch] field value be different to the
Variable value;
* in uStore Admin, I would use this Variable as a Dropdown List (whose
contents could be either hardcoded or populated by a "Select Distinct"
SQL query to an SQL database).

You will already see the following limitations:
* uStore pricing will be wrong (as uStore will take all the data
source records into account, without applying the Plan's "Skip"
logic);
* the uploaded data source preview table will also include all records
(as the "Skip" function is only applied during the composition step,
far later);
* on huge databases with few printable recipients, performance issues
may arise (as the whole database will be read).

Michael Bova

unread,
Jan 12, 2010, 11:48:12 AM1/12/10
to xmpie...@googlegroups.com
Thanks Bill. If my databases would be static, I would say the easiest would be to split it up by branch. Since they will be fluid that makes updating them time consuming. I was looking for an easier solution :)


Michael Bova

Reply all
Reply to author
Forward
0 new messages