Due Date is this week or next week forumula


I’m trying to come up with a formula to denote if something is due “This Week” or “Next Week” but can’t seem to nail it down. I’ve tried using this:


Airtable accepts the formula, but I get an #ERROR in the field. I’m just looking for it simply to return a “1” or “0”. I also need to denote Next Week in another field, which I was planning to build off this formula if I got it working. Any help is appreciated.


Hi there! I’m no expert, but I think maybe you’re returning an error because the function “IS_SAME()” is trying to compare two dates, while “WEEKNUM()” is returning only numbers.

If you change “IS_SAME()” to an “=” sign, it should it work.

IF(WEEKNUM({Due Date}) = WEEKNUM(TODAY()), 1, 0)


Appreciate it. Got it working now.


FYI, if you are only comparing using WEEKNUM, and you have records that may eventually span over multiple years (past or future), this formula will end up buggy because you’re not taking years into account. For example, we’re currently in week 44 of 2018, but if you had records with dates of week 44 in 2017 or 2019, they will also be incorrectly marked a 1 instead of a 0. I’d recommend comparing week year and week numbers combined together, I think more robust formulas would be:

  • 1 if current week:
  • 1 if next week:
  • 1 if current week OR next week


Awesome, and excellent point. Luckily we’ll just be using the records for a month and be done with them. Definitely will keep this in mind though, thanks!


I think I’ve found a “Sunday night” (or localization?) bug in Airtable’s date functions…
At 10:38 PM PST on 2019-01-06:
DATETIME_FORMAT(“2019-01-06”,‘GGGG-WW’) returns “2019-01”
DATETIME_FORMAT(TODAY(),‘GGGG-WW’) returns “2019-02”
Hopefully, the functions will work as expected tomorrow.


You’ve run into a situation where one of your calculations is using GMT and the other isn’t. If you wrap the dates in SET_TIMEZONE(), both formulas will report based on your local date:


You can find a list of valid location identifiers here.

Lookup field not pulling the correct date