Posted: November 13, 2012 at 3:13 am
|
Hello , we would like to buy the Business License for Registering users and booking option to our Venue We need something like For eg. If someone wanted today to book a seat between 15.05 and 15.20 he would be assigned the UNQ000001 is the unique ID starting from 1 to UNQ999999. So if someone registers for the first time, we want to have a unique ID (in this case the UNQ000001) while if he books again ,the system should know the user is already registered . So he will have 2 bookings in the history of the system for the same user. For eg One as UNQ000001_13112013C01S01 and another one as UNQ000001_15112013D14S09 Also ,we want to assign a payment method (Cash) with this setup. Is this doable?? Thank you |
An event calendar and registration are built-in features of Event Espresso. So is having Cash/check as a payment method. What you’re asking for what sounds like a custom registration id for each attendee would need to be custom developed. However we do have a unique identifier for each attendee, but no, they are not tagged with a specific code for each attendee, they’re just randomly-generated. |
|
|
Thanks for the response. Is there a way to have this ID,so we can develop a workflow for tagging this with our registered users? Is it internal or after a registration we can have knowledge of this unique ID so we can tag it with the registered user and his email?? (For eg. in a custom XL sheet) Thx |
The registration ID is created when the attendee is created (which happens when they submit their information in the registration form). Again, though, there is no common prefix like what you were describing. If the same attendee registers for 5 events, they’ll get 5 different registration ids. You would need to either use the WP User Integration add-on and require the user to register for the site (in which case you could pull up their WordPress user ID) or custom develop a solution that gave everyone with, say, the same email address a specific registration ID prefix so all registrations from the same attendee could be pulled up explicitly. FYI, this will be completely unnecessary in 3.2 which is in development, as pulling up information about specific attendees and what events any single attendee has registered for will be built-in functionality in 3.2. |
|
The support post ‘Unique identifier-Bookings’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.