Right now, when constituents register for an event in NXT, we have to pull lists from BOTH systems to see all the data points needed. We always need things like constituent attributes/custom fields, assigned solicitor(s), constituency code(s), multiple email addresses, detailed alumni information, business information, lifetime giving information, NXT-specific event participant options (which don't show AT ALL in database view) and THEN merge the two lists together in Excel and slice and dice as needed.
This is obviously time-consuming, more likely to have user-errors, and difficult for people without super excel skills....
Either everything should be available to export from NXT Events (or web view query) or in database view (Query --> Export).
In particular, we need to be able to view the assigned solicitor in participant lists in the events module. Blackbaud has a real chance with NXT to correct some of the fundamental issues with the events module, so I hope the opportunity is taken here.
My idea was merged into this idea, but it's not exactly what I was looking for - although the above would be great, too. I am still frustrated that the specific view/columns I select for a specific event don't stay intact when I change the view and columns in another event. Not every event requires the same columns in the participant list for viewing or exporting and having to select these every time is time consuming and is really confusing for other users when I direct them to a list and they don't see the same thing.
agreed- very difficult at this point the event module is missing so much that is used in db view. Will the additional tabs ever show and be usable in NXT? Making these all "custom fields" does not give the functionality needed. The insights dashboard also does not provide a filter for just sponsor level (we add to participation level, registration fee and gift package and none of work for event insight on dashboards). We use travel for conferences out of town to navigate the airport shuttles needed and the rooms so we can deliver messages as one example.
Another issue is being able to edit some of the fields in webview. For example, participant custom fields can be seen in webview, but not edited. It is very difficult to manage event data with these kinds of barriers.
The ability to export all fields would be a major time saver. This is also a major barrier for some organizations to adopt web view event management and registration forms.