When we set up each individual form, we cross-referenced it with the proper appeal. Events are not one dimensional where we only sell tickets. We sell tickets, raffle tickets, sponsorship packages and ads, so to make the appeal one dimensional is not efficient for the gift processing team, When utilizing the RELO and the information is downloaded, we can see the proper appeal in one of the LO attribute fields that is downloaded. As a work-around, our template batch has this field next to the appeal field for quick entry. We shouldn't require a work-around because the proper appeal should be downloaded with the batch. From a design standpoint, I guess the 'Event' in LO can be an umbrella and each form can merely be attached to it somehow. And when we cross-reference the Event, the codes on the Event SHOULD NOT replace any cross-reference codes on the forms.
I'll vote for this WITH THE CAVEAT that if you DO only need to map to one appeal code (which our organization does), we shouldn't be forced to set up mapping at the ticket type level. We should have the option to map at the event level.
Thanks for the great suggestion. As we focus on the next generation of Luminate, we'll take this idea into consideration when working on Calendar Events and the underlying need for greater parity between Luminate and The Raiser's Edge.
Yes, curretntly all the ticket levels are cross-referenced to the same appeal and the same package codes. If each ticket level could be cross reference to their specific package that would be extremely helpful. Right now we have to look at ever gift amount fpr the event to see if the package code need to be changed.