Calculate Dates and Excluding Holidays

Hi Kiersten! Im interested in this, as an idea would you be able to display validation logic? 
So if it hit a particular date it would reject it. 
Also i have no idea how to code that, just random idea. Also following for any good solutions as i have a similar issue that appears on request forms! Its great at calculating the business days but not 4th july etc. 

I’m not aware of a way to exclude holidays directly in WF.  Holidays/Non Work Days are a collection of Schedules.  I was able to play around in Fusion and exclude them.

I created two project test fields--DateStart and DateEnd-- and populated with them with respective values of 11/23/26 and 11/30/26.  We have holiday exceptions of 11/26 and 11/27.  Using the standard WEEKDAYDIFF/weekDayDiff functions in WF or Fusion yields 5 (instead of the desired 3).

In Fusion I mapped the non work days to an array and used the weekDayDiff function to give me a baseline difference between my two dates.  I then iterated through my array and filtered for those bundles with a holiday date falling between my start and end date fields.  I counted the number of bundles that passed through the filter and subtracted that from the weekDayDiff baseline to give me 3.

This is just a rough idea, so I didn’t include a trigger module or a module to update a custom field with my final calculation (it also only works with whole-day holiday exceptions).

I agree it would be great if we could specify holiday schedule IDs in order to exclude their exceptions from calculations.

I have used this on one of my project calculated fields ROUND(DIV(WORKMINUTESDIFF({DE:Revision 1 Upload Date}, {entryDate}, “schedule ID”),60),2)  It will caculate the time between entry date and when something comes back on proof but you can use any 2 date fields, then the associated schedule that has the holidays indicated.

Hi ​@KierstenKollins , great solutions above already. Just wanted to add a bit more detail  @Stacey_Robertson ‘s  approach since it's likely the option for your use case.

WORKMINUTESDIFF does accept a schedule ID as a third parameter, which tells the calculation to respect that schedule's holiday exceptions rather than defaulting to the system schedule. The syntax shared works well: ROUND(DIV(WORKMINUTESDIFF({startDate},{endDate},"yourScheduleID"),480),2)

A couple of things worth knowing:

• If your forms are attached to projects that may use different schedules, you can use the keyword ScheduleID instead of a hardcoded ID on a project-level form: WORKMINUTESDIFF({startDate},{endDate},ScheduleID) , this will dynamically reference whatever schedule is assigned to that project
• This approach only works for calculating differences between two dates. If you need to calculate a future due date, that's where it gets more complex and Fusion or manual override fields may still be needed

For the 8 calculated fields, if all projects use the same schedule, hardcoding the schedule ID is straightforward. If schedules vary by project, the ScheduleID keyword approach is the more scalable option.