I am helping a non-profit setup a raffle. They have 20 baskets of prizes, gift certificates, etc. They are only selling 20 raffles per basket. Is there a way to limit the number of products that can be added/sold for a form?
PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.
Product Field, limit submissions, out of box possible?
-
Posted 13 years ago on Monday October 3, 2011 | Permalink
-
You can limit the number of submissions per form. So, if a submission is a ticket purchase, limiting submissions to 20 would work? Or is it more complex than that?
Posted 13 years ago on Monday October 3, 2011 | Permalink -
It is more complex than that. There are 20 baskets, and one form. So they can buy a raffle ticket for 3 items at once. But right now all I know how to do is limit the number of form submission as well. It might not be possible, I can see it being useful, but I can also see it being a feature that might be to "shopping cart" and not make the cut... I was hoping there was an advanced feature tab or something that I am missing for the products.
Posted 13 years ago on Monday October 3, 2011 | Permalink -
I'm not 100% sure what you are trying to do. Are you trying to limit how many products they can order? Are they only allowing 20 raffle tickets of each basket to be ordered across all users or only limiting individual users to purchase 20 raffle tickets for each basket?
Posted 13 years ago on Monday October 3, 2011 | Permalink -
Correct Carl, 20 total per basket across all users. Everyone has a 1 in 20 shot in winning if they purchase 1 raffle ticket.
Posted 13 years ago on Monday October 3, 2011 | Permalink -
Currently there is no built in option to accommodate this type of setup. It may be possible to do using custom code by querying the data and then implementing some custom code if more than 20 of a particular basket has been purchased.
What you could do is query the entry data for entries that have a payment status of approved and have been paid for and check for the total number of baskets ordered per basket type. If it's over 20, then inject some custom CSS on the page to hide that field by setting it to display: hidden.
It's not ideal since technically the field is still there, but it would probably be sufficient for this situation.
I would like to implement more advanced functionality in the future to be able to do things like this out of the box, but it probably will not happen until we do an overhaul of the form editor UI which gives us more flexibility to add more advanced features on a field by field basis.
Posted 13 years ago on Monday October 3, 2011 | Permalink
This topic has been resolved and has been closed to new replies.