Hello,
We have been running into the same road block a lot lately, and I am wondering if anyone else is having similar problems with List Manager.
The RWB School uses List Manager all of the time to generate all sorts of unique lists. Lately, in the last week or so, all of the lists we create are generating zero constituents. We are using the exact same criteria as years passed, just with newer performances or other unique information. This even happens when we add associations as part of the criteria to the list.
Does anyone know what's up? We greatly appreciate any and all help!
Hi Tali
A lot of List Manager elements are based on Ticket History.
If your Ticket History update proc is having a problem, that could cause some data that the lists are based on to be missing or misconfigured, which could result in zero hits.
In particular, a lot of Ticket History update scripts (usually handled by a SQL Agent Job that runs overnight) require you to specify the seasons to be updated manually. (In the Job script.)
That's the default setup, in fact (certainly it used to be). We changed ours to automatically update all active seasons, to avoid the need to add new seasons manually whenever they're created. That means a lot of unnecessary updates happen, but it's safer, and less prone to Unfortunate Events.
That's just one possibility, of course.
Ken
We were having a very similar problem at the turn of the year, and it was because the ticket history and package history was not including the new year's seasons. Once we adjusted the job, all went back to normal. :)