Hello All,
I've been looking to customize my Formidable Forms (Pro) Date fields, so that when I set minDate values to say +3 days or +10 days, the date picker bases that off of business days, and does not include weekend days.
As it currently stands, I'm able to set minDates for + 3 days, +7 days, etc. and the datepicker works fine basing that minDate value off the calendar dates.
I've currently set up Sat/Sundays as well as my company's observed holidays as blackout dates, and the datepicker respect those blackout dates. If a due date falls on a blackout date or a weekend, it advances the next available due date to the next non-weekend/non-blackout date. I should also say this form is a multi-page/AJAX form and I think that may be causing some issues with implementing this feature.
Has anyone had success in getting this functionality to work, where the minDate value is calculated based off of business days?
I've gone through the docs and tried to get this to work, and have run through a couple of different approaches and tried a couple of methods but can't seem to get this to work at all.
Any insight/help is appreciated. Thanks!
I'm a little confused by your question. You title says you get the Date/datepicker fields to use business days instead of calendar days. Your first paragraph says "when I set minDate values to say +3 days or +10 days, the date picker bases that off of business days, and does not include weekend days." This is doing exactly what your title is asking. What are you trying to accomplish? And, have you seen this Knowledgeable content: https://formidableforms.com/knowledgebase/datepicker-options/
I've read through that page. And sorry about the confusion. I meant to say that it's using calendar days when it makes it's calculations. So if I needed +7 business days from today, the datepickers are showing a minDate of next Thursday, 10/2. But if it were working the way I want it to, it would calculate +7 business days, which would land on Sunday, 10/5. Since I've already set Saturdays and Sundays as blackout days, the form then moves the date up to the next non-blackout day, which is Monday, 10/6.
At the end of the day, I'm trying to get it so if I were to need +7 business days in the future for a minDate, it does not count calendar days that fall on any sort of blackout days I've set up in the field settings.
And thanks for responding to this thread!
That's exactly what blacking out weekends does. https://formidableforms.com/knowledgebase/datepicker-options/#kb-blackout-weekends.
<p>I don't think it does though. I've attached some screen shots of what I currently see. You can see I have the weekends blacked out, as well as about a dozen holidays. Today is 9/26/25. When I set the minimum date to 'Current Date' and '+7 days', the corresponding datepicker shows the earliest date to be picked is 10/3/25. Which is correct if it's calculating 7 days into the future including the blackout dates of Saturday/Sunday. If the plugin were calculating based off business days only, the earliest date would be 10/7/25. Perhaps I'm not setting something correctly in the field options, but I'd assume current date +7 days would be correct.</p><p>Thanks again for your help!</p>
It's possible you've encountered a bug. It's been a long time since I've had to anything with the datepicker or date math. I suggest you open a ticket and report a suspected date math error. Open it as a bug report so it receives the attention of the Strategy 11 developers.
If the Strategy 11 developers confirm a bug, they'll fix it in a future release. You may even receive a patch to use in your system to confirm the bug is fixed. I don't know how the support team handles these requests nowadays, but this is how they worked with me when I've opened a bug ticket in the past. They're very responsive when fixing bug reports if it's not related to your custom code.
Speaking of custom code, if Strategy 11 finds that this isn't a bug, but how any 3rd party libraries work, the work around is custom code written in jQuery. You will need a function to provide the correct calculation when the form is rendered for display in the browser.
Thanks for your insight on this. I'll open the ticket with them and update this thread with any new information in case someone has this issue in the future. Thanks again!
Please login or Register to submit your answer