Hi,
I really hope someone can help. I am trying to sort out our best available function because it keeps allocating seats across an aisle which is not very useful. I have checked the contiguity and teh seats do not have consecutive numbers and I have tried changing the fill patterns and priority with no success. Has anyone else had this issue and how have you resolved it?
Thanks
Kerry
Kerry,
I am far from an expert at this, but the one thing that initially occurs to me is to ask, are any non-seats between these two aisles labelled for contiguity? I seem to recall that working best when even non-seats are labeled for contiguity even though it seems like an odd thought labelling non-seats.
If there are no non-seats between these two aisle seats, I think you have to have distinct logical seat rows between these seats.
Again, I am far from the authority, but I hope that this might help!
John
Thanks Jon, Yes all no seats are labelled which is why this is baffling me so much.
I suppose you could try manually changing logical seat rows, so that they are different?
I just found this on the documentation on Contiguity on the website: "If non-seats, such as an aisle, separate seats in a row they should be included in the block and should have contiguity values applied to them. Applying contiguity to the non-seats causes the seats on either side to have non-consecutive contiguity seat numbers, meaning the best seat function will never select them as a pair."
So if that is what you have, and it is still selecting them as pairs, you might try opening a support ticket.
Last thought. Is this a venue already in use? And/or, are you deleting and re-creating the pricing structure for your test case after making changes to the map? I do not recall anything specifically about contiguity being mentioned, but it seems logical to think that it might be part of the updates in the facility update utility. So you might have to run that against the season for your test case.
Best of luck!