There are a couple of things that are great about this portal. I'll start with the pro's first..
1) It's great that the participants don't have to be downloaded like they did with OE. This is a huge time savings.
2) It's also great that the registration fee does not get automatically saved in their gift record since a lot of the registrations truly the cost to attend an event and no taxable amount associated with it
Now the cons...
1) While it's great you can add participant options with the registration, why is this information not able to be shown as an available column when exporting the information? In my case, it's something I want printed on the nametags and can't find anywhere to export this information.
2) Why does the system automatically assign a new constituent to all "hosts"? Our system is set up that the husband is created as the constituent and his wife is a relationship under the husband (parents at a school). The event I set up is something for the Mothers/students and now NXT has assigned new constituents to all the Mothers. So after the event, I will either have to delete all of the new constituents or tie them to the relationship already established. Either way is going to be time consuming. There should be options when setting up the event to tie to an address when auto-assigning to a constituent (like OE does).
3) Need to be able to add a name tag field to easily create name tags from the export.
How is your registration fee not getting automatically saved in the gift record? When we approve the event registration through batch in NXT, the registration fee is posted to the gift record and the only way to adjust it is to break the gift link on the events tab, which is all a very manual process.
I do not see anywhere to add participant options to the event. I have checked all available columns.
Thanks for your comments here!
I did want to point out a few things in your cons list that may help you:
1) Participant options ARE available as an additional column. You do need to go to the Columns options and add these to your event. Since these are individual to each event, they are NOT sticky so you'll need to do this for each event you're working with. You can also filter by participant option values.
Once you add them as a column, they're automatically included in the export.
Give that a try and see if it works for you.
2) The main person filling out the form does have to be a constituent right now. We are evaluating changing this for free events (participants who make a payment will always have to be a constituent record.) I would recommend voting for this idea which I believe is in line with your request. https://renxt.ideas.aha.io/ideas/RENXT-I-4059
3) We don't support name tags in a first class way yet (vote for this idea to track any progress we make on this: https://renxt.ideas.aha.io/ideas/RENXT-I-2636.) I have seen customers use a participant option for Name tags. This way it can also be included on the registration form for participants to enter their own name tag info, or you can keep it managed from the participant record in webview. You can then add that particular participant option as a column on your participant list and it will be included in the export.