# Better Dates in Fibery. Dates as Databases

**URL:** <https://community.fibery.io/t/better-dates-in-fibery-dates-as-databases/10117>\
**Category:** Fibery Showcase\
**Created:** [December 1, 2025, 2:09pm UTC](https://community.fibery.io/t/better-dates-in-fibery-dates-as-databases/10117 "2025-12-01T14:09:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [December 1, 2025, 2:09pm UTC](https://community.fibery.io/t/better-dates-in-fibery-dates-as-databases/10117/1 "2025-12-01T14:09:01Z")

</div>

Hey!

My first public integration: Better Dates. See info here: [Fibery](https://integrations.fibery.io/@public/Public/Integrations-27#Public/Integration/Better-Dates-1)

Add a custom integration, then put in this link: `betterdates.fiberyintegrations.com`

It’ll give you the ability to integrate Days, Weeks, Months, Quarters, and Years into your Fibery Workspace.

The timezone is important for it to know which day is “Current”, and you can set to update every hour.

This useful in making KPIs, resource allocation, “today” functionality in different timezones, viewing entities grouped by week, month, outside of reports, and probably more I haven’t yet thought of.

For simple setup, just add a one-to-many relation to “Day” auto-linked by the date. Then you can pull the Day.Quarter, Day.Year, or anything else you need directly onto your entity.

For more complex setups like resource allocation (incl all the days between two days) you’ll need to use an automation that runs when the daterange is updated. Something like this:

```auto
Days.Filter(
  [Date] >= [Step 1 Timelog].Dates.Start() and
    [Date] <= [Step 1 Timelog].Dates.End()
)

```

Curious to hear what other use cases this might have!! Enjoy!

If there are issues, please let me know!

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [January 10, 2026, 4:56pm UTC](https://community.fibery.io/t/better-dates-in-fibery-dates-as-databases/10117/2 "2026-01-10T16:56:34Z")

</div>

Using this thread as a changelog for now.  
There was a bug with how weeks were being calculated, and how it was handled across years. This has just been fixed, please do a full sync to ensure things are up to date.

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [January 15, 2026, 1:11pm UTC](https://community.fibery.io/t/better-dates-in-fibery-dates-as-databases/10117/3 "2026-01-15T13:11:58Z")

</div>

> [@January 15, 2026 / police\_officer Validation rules, New Connector styles and options, “Periods” integration](https://community.fibery.io/t/january-15-2026-validation-rules-new-connector-styles-and-options-periods-integration/10247):
>
> police_officer Validation rules Today we’re introducing new concept in Fibery — Validation Rules. Validation Rules in Fibery help keep your data accurate and consistent. Think of a validation rule as a bouncer at a club door smiling_face_with_sunglasses. Before any data change gets in, the bouncer checks: “Does this meet our standards?” If not, the change is blocked and the user gets a friendly explanation of what’s wrong. A validation rule fires when its condition is true, and it blocks th…

Fibery released an official “Periods” integration.

The biggest difference is that it puts all period types into one database (Days, Weeks, Quarters, and Years), where the one I made splits them into separate databases. Both have pros and cons. I’ll play around a bit more with the official one and provide a better breakdown.