Participant options RENXT vs Database View

Neil Marshall

Hi,

Users of the system we're currently working with use Database View quite a lot as opposed to RENXT (although they're using that more and more). It is clear though that they use both systems and are more comfortable with Database View short term.

We have an event registration form on a separate system that uses the SKY API to add participants.

When it comes to events and participant options, Database View and RENXT don't seem to be able to see the same information. Participant options in RENXT can't be seen in Database View, and in fact there doesn't seem to be anywhere to manage participant options within the Event record.

Would this be a correct interpretation?

We're using the SKYAPI to add participants to an event however if participant options are selected during the registration process, they can't be seen in Database View and therefore could be missed.

If using OLX to register participants, you can select participant options that are available in Database View, but these aren't visible in the RENXT.

Is there any route to allow participant options that are available in both Database View AND through the SKY API / RENXT?

Many thanks.

Justin Muratore

@Neil Marshall
Thank you for your post! Participant options are only available in web view and there is not a way to view or manage them from the database view. What you may be thinking of for Online Express is a participant attribute that is tied to an attribute in the database view. Participant options in the web view are unique and are not the same as participant attributes in the database view.