Can someone share their recipe for a Dynamic list that we can use for triggered performance reminders in WordFly? We'd like to send these 3 days before the show and we want to specify the production (25 performances occur within a production.) Frankly, I'll take any and all recipes for performances reminders and we can cobble it together. A screenshot of the criteria should do it.
Margaret Lehtinen
Indiana Repertory Theatre
mlehtinen@irtlive.com
I'm putting Heath's emails below for everyone:
Hey Margaret,
So this is from 2019 but we use the same procedure
And then regarding the Output set:
Ahh … I did that myself. I set up a local view for the Next Performance (attached).
Output is Customer_no, Perf_name and perf_dt
Otherwise you might be able to set up a TR_QUERY_ELEMENT_GROUP from https://community.tessituranetwork.com/tessitura_software_forums/f/tessitura_ticketing-0/10587/output-set---next-performance
H
USE [impresario]GO
/****** Object: View [dbo].[LV_NEXT_PERF] Script Date: 11/10/2021 11:57:25 AM ******/SET ANSI_NULLS OFFGO
SET QUOTED_IDENTIFIER OFFGO
CREATE View [dbo].[LV_NEXT_PERF]ASSelect distinct pn.customer_no, pn.perf_name, pn.perf_dtfrom VS_TICKET_HISTORY pn JOIN (select th.customer_no, perf_dt = min(th2.perf_dt) from VS_TICKET_HISTORY th Join (select customer_no, perf_dt from VS_TICKET_HISTORY where perf_dt >= GETDATE() ) th2 on th.customer_no = th2.customer_no group by th.customer_no ) thd ON Cast(thd.customer_no as varchar(20))+Cast(thd.perf_dt as varchar(20)) = Cast(pn.customer_no as varchar(20))+ Cast(pn.perf_dt as varchar(20))
GO
Heath, Thank you so much for this! Clearly is was really needed by this community and you are an angel!
If someone is in a scenario where they need near real time or plans on using something like this to send post visit e-mails and is in a situation where tickets can be upgraded to a membership I would highly advise against using any of the ticket history tables for this kind of thing as they will miss customers.
In a related scenario regarding building the criteria we had a situation where WF was crashing after about 8 months of operation due to the volume of duplicate customers being sent up each day based on the Criteria logic. While this is interest and not tickets the same logic could easily be applied to tickets as well.
IF OBJECT_ID (N'dbo.LFT_MBA_NewInterestsByLists', N'IF') IS NOT NULL DROP FUNCTION dbo.LFT_MBA_NewInterestsByLists; GO CREATE FUNCTION dbo.LFT_MBA_NewInterestsByLists ( @KeywordNo INT ,@ListNo INT ) /*Docu Date Created: - 06/03/2021 Created by: Ronald Radford/Jon Shaffer Purpose: Pull list of customers based on interest who have not previously received notification @KeywordNo INT -interest to check for ,@ListNo INT - List number bing used in Object Notes: This is a stop gap solution, at some point when the other fires are taken care of we will need to circle back and build a a logging table for tracking the customers as there is the potential for some to be missed if WF experience an error on last run. */ RETURNS TABLE AS RETURN ( SELECT * FROM(SELECT customer_no , MIN(create_dt)as CreateDate, count(*) as Hits FROM TX_CUST_TKWwhere tkw = @KeywordNoAND selected = 'Y'GROUP BY customer_no) as K WHERE CreateDate >= ISNULL((SELECT MAX(DateLastUpdated) FROM LT_WF_EXPORTWHERE ListNumber = @ListNo), DATEADD(day,-1, GETDATE())))
To get the list no for a new list you have to save the list first and then update the function with the list number. Here is how it is used in the list: