(I'm cross-posting this to a couple of forums; apologies to those who get multiple copies...)
Tessiturians -
I am currently working with our DBA to investigate the possibility of creating an order confirmation email that can be used by our financial aid staff. Currently, we use an excel sheet (shudder) and a Word/Outlook mail merge (shudder again) to accomplish this. Ideally, it would be infinitely better if the staff person could just send a confirmation right from Tess instead.
The problem we are running into is including some custom data in these confirmations. Our DBA and I have only a small smidgen of experience with Web API stuff, but from reading the documentation we are unsure about bringing in some of the data elements we'd like to have on the confirmation. Specifically, the name of the Recipient for each line item, and the total financial aid disbursement (which is recorded on a custom screen on the constituent record).
Does anyone have experience with doing something like this?
Thanks!
Patrick SchleyAcademy Services ManagerFirst Stage
Unknown said: I am currently working with our DBA to investigate the possibility of creating an order confirmation email [...] The problem we are running into is including some custom data in these confirmations. Our DBA and I have only a small smidgen of experience with Web API stuff, but from reading the documentation we are unsure about bringing in some of the data elements we'd like to have on the confirmation. Specifically, the name of the Recipient for each line item, and the total financial aid disbursement (which is recorded on a custom screen on the constituent record). Does anyone have experience with doing something like this?
I am currently working with our DBA to investigate the possibility of creating an order confirmation email [...]
We generate our e-mail order confirmations, selected e-mail contribution acks, and some sub renewal e-mails, all containing significant custom data, and all generated in HTML entirely within our impresario database via a custom stored procedure.
Very complex, not for the faint of heart, but once you've created one, I predict you'll do more...
Happy to share code; please e-mail offline if interested.