Hi team,
I’ve created a system for my database where people can create events via a shared form view (and get points for doing so). The issue is, anybody can create post-dated events and that could screw up the system a bit.
Would it be possible to have a toggle in the date option “date must be posterior to today” ?
Thanks in advance
Hey @Paragon, I’ll discuss the feature requests with the team, thanks for sharing it! 
Hey @Paragon, unfortunately, we’ve decided not to implement this feature idea. We think it’s a more advanced use case, and implementing just one validation rule would likely lead to requests for others. Since we don’t have a plan for adding validation rules right now, we can’t move forward with this.
But, our Application Builder might be a better fit for your needs. We’ve already implemented the form validation feature there (see the screenshot below), and I’d be happy to check if we plan to add the specific validation you mentioned if you’re interested in using Application Builder.
While I’m sad to hear this, I understand the point.
Such features would be really useful for organizations such as mine that rely on forms as a way for “outsiders” to modify the database.
Having the ability to prevent people from creating events back in 2010 would surely be useful.
As far as field validation goes, since people are also making lots of honest mistakes (wrong phone number or email address), those issues make debugging a nightmare that could be avoided if some field validation guideline were available.
What could I do to make this a higher priority for the dev team ? Should I find other people in the community to “vote” for this option ? (does this meta-feature even exist ? :'D)
(I haven’t gone into the App Builder yet, I’m waiting for the Expert formation)
Hey @Paragon, I understand your point. If we see more people asking about this feature, we will discuss it again. 
Even if the request is accepted, we will first need to introduce field validation in the database, and then we’ll need to build more advanced validation logic, as you mentioned. So even if lots of people upvote, that won’t happen soon (just want you to know).
This feature already has a high priority score: Field value constraints (#647) · Issues · Baserow / baserow · GitLab. I recommend you add your comment there so developers can consider your date validation request while working on it. 
Thanks for the link, i even found a comment by Bram Wiepjes 4 days ago that said this was in development 
You guys are way quicker than I thought haha
I’m thinking if the :
A numeric field’s value must be within an upper and/or lower bound
is implemented, dates should be included so it’s perfect for me !
Nice, this one is the most requested by the community, so we decided to implement it, yes. 
