I’m looking for the ability to make it so that a user can only book a resource once per day.
Example: They can only book Tennis Court 1 for 9AM on Today. They cannot also book it for 4PM on Today.
Hi Dude,
This should be achievable using the GP Limit Submissions perk. I’m not fully sure how your booking form is configured, so I can’t recommend the exact setup, but in general, the perk can be used to limit each user to one booking per day.
If you’d like more specific guidance, feel free to reach out to us at Gravity Wiz support and include an export of your form, we’ll be happy to take a closer look and help you set it up.
Best,
My apologizes for not explaining that in depth.
The user should be able to book multiple bookings via the form in a day — use the form more than once in a day. But we don’t want them to be able to book multiple courts on the same day.
Example:
- I can book court 4 for today, but I cannot also book court 3 today.
- I can book court 4 today for today, and I can book court 4 for tomorrow.
Hey Dude,
No worries at all! That use case makes a lot of sense, and with a little help from GP Populate Anything, this should still be possible using GP Limit Submissions.
Now, there’s probably a few different creative ways that could get you these results, but here’s a pretty straightforward one that uses the idea of limiting by a group of field values:
For this use case, the specific values we need are 1) the user submitting, and 2) the court booking date. If I understand correctly, each combination of 1) and 2) should only be allowed once, as a person can only make one court reservation (regardless of the court they choose), per reservation date.
Value 1 can be grabbed using a hidden Single Line Text field and the {user} merge tag. I would personally use {user:user_email}, as that’s going to be easy and unique for the currently logged-in user.
Value 2 is trickier, but can be captured using a hidden Date field, and a GPB specific merge tag. For this example, you could use something like @{Booking time:1:startDate}, which will grab the reservation date selected in Booking Time Field 1. (Just swap “1” for the Field ID of your own Booking Time field).
Finally, with those two values being captured, you can then set up a rule group in your GP Limit Submission feed that then checks for unique combinations of both:
This approach should work as of Version 1.0-beta-2.3 of GP Bookings, and if this gives you any trouble, please just give us a shout via Support! We’ll be more than happy to take a look at your current setup.