Configuration
- Unit — the calendar period one entry covers.
- Every — how many units per entry. Week × 2 is a fortnight.
- Alignment — Calendar snaps entries to real month/week/quarter boundaries and trims the first and last to fit the range. From start measures every entry from the start date instead, so they are all the same length but land mid-month.
- Max periods — a safety cap. Asking for days over a decade is almost always a mistake, so the node refuses and tells you the count instead of running.
Inputs
- In — the range to split. Both ends must be closed: an open range has no first period, or no last one.
Outputs
- Periods — the list of ranges, in order. Each is a date range you can feed straight to a step’s Date range assign.
Tips
- The periods are contiguous and never overlap, so a record dated inside the original range belongs to exactly one of them. That is what makes it safe to merge per-period results without de-duplicating.
- Weeks start on Monday.
- Bounds are read as whole days. Splitting an intra-day window is not what this does.
- Doing this only because an API rejects a wide range? Check the step first — the ones with a vendor period limit tile internally already, and one wide range is both fewer nodes and a single cache entry.