-
-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NextGen Checkin-Override makes you choose a service #6204
Comments
@kimlongcr With that same check-in configuration, if you don't do an override, does it still show both service times or does it auto-select the 11:00am as the only option? |
@cabal95 It auto selects the correct time. |
@kimlongcr I haven't been able to replicate this yet. So there must be something in the check-in configuration that I'm not setting the same way. Can you try selecting the 11:15am service in override mode and see what areas/groups come up as possible choices and see if that provides any additional clues to what configuration might make that schedule show up? i.e. does what show up use a DataView filter, or special needs, or whatever other options are configured on that group. |
@cabal95 I just spent 45 minutes trying and can't get it to happen. I reached out to my Kids Club Director and asked her to recreate it. |
@kimlongcr Sounds good, let us know what you find! |
We think this was happening because of this issue. #6137 |
Sure thing! |
Description
When you do an override on the kiosk, it is making you choose a service time even though the kiosk configuration for this site and time is only one service time.

First screen in old version after choosing the kid(s) to override (notice it already chose the service time):
First screen in NextGen after choosing the kid(s) to override:

Actual Behavior
It automatically picks the correct service time based on the kiosk configuration chosen.
Expected Behavior
Service time is automatically selected
Steps to Reproduce
Issue Confirmation
Rock Version
16.8
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered: