# January 15, 2026 / 👮 Validation rules, New Connector styles and options, “Periods” integration

**URL:** https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247
**Category:** Changelog
**Created:** [January 15, 2026, 12:00pm UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247 "2026-01-15T12:00:31Z")
**Posts on this page:** 1
**Showing post:** 21

<div class="post-metadata">

### Author: ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [January 16, 2026, 5:05pm UTC](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247/21 "2026-01-16T17:05:45Z")

</div>

> [@interr0bangr](#):
>
> Why is it an “integration” and what data source is it actually integrating with behind the scenes?

Because (some of) the values change over time (the Relative field and the semantics) and the entities to sync can change over time (if you don’t choose a start year). The latter can be useful as it will save you from having to generate new data every year.

> [@interr0bangr](#):
>
> Any reason why the name formulas can’t be edited? I’d prefer quarters to be “Q# YYYY” to match the “MM YYYY” format instead of “YYYY-Q#”

Because integrations provide only read-only values.

If you don’t need the afore-mentioned functionality, then you can sync once and then disconnect, and it will behave like a normal db.

> [@interr0bangr](#):
>
> I need to have “Year Type” field that has “Calendar” or “Fiscal” options. Like, Jan 2026 could be in both the 2026 “Calendar” year” but also the 2025 “Fiscal” Year as well. And each of our clients may have a different fiscal year, which adds complexity (or maybe impossibility?) as well.

Even if you don’t disconnect, you can augment the db with whatever fields you like, including a ‘Type’ field, but indeed, the integration won’t be super useful if your definition of a Year is not the ISO definition of a year (and we weren’t aiming to address all possible use cases - tax years, fiscal years, etc.)

> [@interr0bangr](#):
>
> I also need a “Week of the Month” field that calculates the relative week (1-5) of the month a day falls in. So a day could be in 2 different years For example for Feb 10, 2026 would linked to the Week with the Number = 7, but also the “Week of the Month” = 3.

You can add the formula described here:

> [@Getting a date's week number within a month (not a year)](https://community.fibery.io/t/getting-a-dates-week-number-within-a-month-not-a-year/8442):
>
> The recent date function additions are awesome, but I’ve run into a new scenario that can’t be solved with them alone I don’t think. I’m trying to get the week number of a month, not of the whole year. So the output would need to be either 1, 2, 3, 4 or sometimes, but not often 5. For example, if the input was “Jan 20, 2025”, I would want the output to be “4” Jan 1-4 - Week 1 Jan 5-11 - Week 2 Jan 12-18 - Week 3 Jan 19-25 - Week 4 Jan 26-31 - Week 5 I have made the following basic formu…

(but the numbers would only really be meaningful for entities of the Day type)

---

_[View the full topic](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247)._