List criteria

Weird, we've also just only encountered this fun feature. (We removed the offending criteria in our case.)

Sadly that's not an option for this list. My poor user is having to make several lists and is being very patient about it.

Thanks for the reply.

Debbie

Again (this isn't a great solution) you could make a view that does some of the work for them.

More interested in this because we hadn't noticed the limitation prior.

I did exactly that, but my view is pulling data from some of the standard tables and I don't define any data types or lengths. I think it's a limitation of the List Builder itself.

Maybe someone from the Network will jump in with words of wisdom. There is nothing in the documentation to cover it.

Debbie

Hi Debbie,

Maybe I'm missing the point here but why not use the Production Season list criterion?  We have one (which I believe isn't custom) called Ticket History Prod Season

Martin

Hi Debbie

I hope you're well.

I would agree with Martin, it should be possible to use a Production Season element which would allow the user to select all of the performances within the Production Season. Are you using the standard Ticket History screen or a custom one?

Regards

Mark

Hi Martin and Mark,

Yes, that almost works. She can't use Production Season, but she can use Production. However, If she doesn't want to select all the Performances within a Production, there is still a limit on how many can be selected. Back to my point, I think this is a limitation of List Manager, I don't know if Mark can verify that.

Thanks for replying, any suggestions are welcome and I have tried this out.

Debbie

Thanks to everyone for the suggestions. I'm using some extra views so that the list criteria can be used to select Section, Row and Seat, as well as Performance.

If I use Production, then the list pulls in everyone who has come to the Performances for the Production on the dates I have asked for, but doesn't filter out those who are not seated in the Row/Seat Number I have specified.

I've tried other lists using Performance/Production/Production Seatson and there is definitely a limit to how many items can be selected from a drop down. Can you confirm that is the case, Mark?

Thanks, Debbie

Debbie,

Someone from Tessitura/RAMP can jump in and clarify if I am reading this wrongly, but I believe that this is controlled by the TR_QUERY_ELEMENT table.  In the Table Definition, the data_select column is VARCHAR(255), and thus, once you get to around 50 four digit numbers with commas (or fewer if you are up to five digit Production/Performance numbers), the Tessitura Client returns an error since it will not be able to put any more information in there.  At least, that fits with the experiences I have had.

By the way, I believe this holds true for ALL List Manager elements; it is just with those performance/production related ones that it ever seems to be an issue because most people are not selecting a list from people with any of 60 different prefix types.

You CAN use multiple instances of the same List Manager element even in the same list definition to get around this character limit.  You can also of course always go into manual edit and add a bunch more numbers if they are known, but it is not as user friendly that way.

John

Thanks John, that makes total sense. As TR_QUERY_ELEMENT is a standard table I can't make any change to it and it might have a knock on effect to something else even if I were able.

We will live with the limitation. It's not been an issue in the past. We just need to pull everyone sitting in specific seats for our Christmas Carol production because the sight line has changed and they need to be contacted. Hopefully it won't happen often.

Debbie

Not the Mark you were asking but...

There is a limit on the number of items that can be selected in a list (I have hit his in the past) - although is not a fixed number of items as the restriction is due to the size of the generated string of IDs separated by commas.

If you have created a custom view for the seat and row data one thing you can do is extend that view to restrict the data brought back by performance keyword.
Setup a specific keyword for this and apply it to relevant performances (this can be done in Season Maintenance) and then add a join to your view to tx_inv_tkw linking on performance number and restricting by the new tkw id.

Users can also search by that keyword in Season manager so there are ways for them to check that the performance list is correct but should remove a lot of confusion with long lists of performance ids within the list criteria itself. I normally add custom views like this to their own category so that all the criteria that can act on the view is together.

Mark

Hi Mark, That's a really good idea. Yes, I had figured that the list limit was down to a field length limitation and our Perf Codes are all quite long, so we have hit the limit.

I'll talk to Sophie about Keywords. I have to co-ordinate with her and not jump in with random codes of my own!!

Thanks, Debbie

John A. Moskal II said:

You CAN use multiple instances of the same List Manager element even in the same list definition to get around this character limit.  You can also of course always go into manual edit and add a bunch more numbers if they are known, but it is not as user friendly that way.

Being wary that if you do so you might be setting up an AND constraint, i.e. customer has tickets to performances 1,2,3,4,5 AND customer has tickets to performances 6,7,8,9,10.  You can use the two panes to create an OR join, but you could only use one element in each.

More tedious, if you need more that two, would be to set up the query in an extraction, where each segment is effectively an OR for these purposes.

Thanks, Gawain!  Meant to add in something about the pitfalls of that method in my post but forgot.