nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Query Web View Participant Options

Steven Talley

I'm trying to move our internal event work for some events to solely NXT. I think we all know how much of a roadblock participant options in NXT are. They don't link back to dbview, you can't get at that data in a flat format unless you manually export from the participants screen, or pull the json from the API and flatten the hierarchy, transform to csv.

Are participant options reachable in Query Web View?

If so, is there some reference with how to format the select fields for participant options in Query API where without Query Web View I can edit a Query with Query API, and retrieve those participant options in a CSV?

Is Query Web View GA delayed? Maybe someone with connections @Erik Leaver can pull some strings and get Query Web View early access for me? Despite requesting to be a part of early adopters program a few times I don't think I fall on the radar, but I would very much like to because I do a lot with data and my data integrations could really benefit from this as soon as possible.

Find more posts tagged with

Comments

Alex Wong

@Steven Talley
@Erik Leaver can answer you about if you can be part of early adopter program, though it would be soon over as i suspect next week PUB will announce it.

Query web view is going to do what Query dbview does only (at this point). Future enhancement may bring “web view” only fields into Query web view, but definitely not there now. So don't hold your breathe.

Steven Talley

@Alex Wong
Yeah, I also suspected next week's PUB might announce GA.
Thanks for letting me know about Query web view's limitations.

No native solution to automate getting flat tables of participant options for the foreseeable future. Did I mention how dumb it was that participant options are siloed?

Alex Wong

@Steven Talley
I agree. Though Participant option is a good idea. The supporting features around it is not well thought out.

Audrey Morris

@Steven Talley Same here - we keep having to tell our people we can't run events through NXT because the ways to export the options they want simply don't exist without an insane amount of work on the back end. It's beyond frustrating since our alternative is the old “registrations” option in BEM, which is clunky at best. We used the events module in RE a couple of years but it was also frustrating for different reasons. We haven't come up with a good solution, so if you find one please let me know!

Alex Wong

@Audrey Morris
@Steven Talley

i took a 2nd look at the SKY API, and wanted to let you know that IF you want and able to go the SKY API route, you can create an export that has the paritciapnt option better listed as the Get Event Participant List API returns all the participant option for each participant of an event. I have not tried this myself so I don't know if there is bug or not, but at least from documentation, you can do it.

Audrey Morris

@Alex Wong Thank you for this info! I will give it a shot on a tester when I get a chance!

SmartTHING Developers

@Audrey Morris @Steven Talley @Alex Wong
Hi,

We have used the below process to sync participant options to participant attributes before:
- Identify events that have not started
- For each event query for participants changed since our last check
- For each export the participant options, along with a generated attribute import id
- Create an import file based on this

It works, but it requires quite a bit of effort. The import ID bit prevents participant options from being imported multiple times. We are considering adding the feature to our SmartSYNC product, but that would be based on demand. If people would like this, please let us know by messaging me or contacting us via the SmartTHING website.

Cheers

Warren

Kelly Bodie

@Steven Talley Is it still the case that participant options are siloed? I'm looking in web view query and still can't find them. I'm rather shocked actually…

Steven Talley

@Kelly Bodie
As far as I understand it will always be the case. In recent roadmap events they've alluded to “reasons” WHY they chose to implement participant options vs participant custom field. I don't know what those are, just that they apparently have them.

@Audrey Morris
I think I missed the responses - and I don't think Alex realized that I was approaching this problem having already used Sky API to pull the data. My problem is that it's not flat. So yeah, you can API call the json object, which is a nested array of each participant, and then their participant options, but then you have to pull out each participant option for each participant onto a new line with the participant import ID and attribute Category for import into database view. For just throwing together a low-code like MS Power Automate it's a bit too intensive and in my experience wasn't reliable.

So I don't try to duplicate that data across anymore. For simple registrations I'll use NXT event reg and tell people to only work with those in NXT. For complex I use Event module/netcommunity and have them work in Database View. At least with query API I can now more easily pull data from both places for our PowerBI reports/dashboards without prior transformation--query result csv for bbnc registrations, participant option json for NXT registrations.

Kelly Bodie

@Steven Talley Thanks.

Anyone - can you point to the roadmap Steven mentions? The May PUB made me believe the opposite — that it was in progress as they completed query work this quarter and moved into Export work. I'm eager to find some hard information so I can plan my work.

Steven Talley

@Kelly Bodie
My apologies, it wasn't a PUB, it was a town hall - https://youtu.be/X5OL6ARb6LE?si=dwJniyWrT2w7DlqL&t=1105.
Turns out they did give a reason why - which was really just because of the large participant attribute table for clients with large numbers of attributes unique to each event. So, yeah, because of the way they are structured, they'll never be able to match 1 to 1.

Yes, it is possible (hopefully probable) that they'll eventually add this to query or export web views so that we can automatically get a flat file of those, but we're okay for the time being, and hopefully NXT event reg eventually improves enough to be a true replacement.

Alex Wong

@Kelly Bodie
Query in webview is based off of query in dbview. dbview does not have pariticpant option, so query in webview doesn't neither. It is something “sort after” by those that uses event module on RE NXT, so I'm sure there is an idea out there to vote on.