Better Dates in Fibery. Dates as Databases

Fibery Showcase
1

Hey!

My first public integration: Better Dates. See info here: Fibery

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:

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!

5 Likes
Habit Tracker into my all-in-one Fibery setup
Dates as first class citizens (in a database and as entities)
Date out by a whole day
Beta testers wanted
2

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.

3

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.