Calendar Pro

Month, week and agenda views over a flat table of event occurrences. Reports the date window it is drawing so the host loads only that window, and raises events when a day or an event is tapped.

It writes nothing and it does not expand recurrence. A repeating series arrives already materialised, one row per occurrence. That constraint is the reason it works against a real list rather than only against a demo collection.

The idea in one paragraph

Most Canvas calendars either compute occurrences at render time, which means no occurrence has a row you can attach an approval or a comment to, or they load the whole list and filter client side, which stops working at the delegation limit. This one does neither. It tells you which forty two days it is about to draw, you load exactly those, and it draws them. The query stays delegable and bounded no matter how large the list behind it is.

Properties

Input

Events table shape

A multi day event is several rows, one per day. See the contract for why.

Config

Output

Events

Implementation details

RangeStart and RangeEnd follow the view. Week draws seven days and month draws forty two, so the toggle raises OnRangeChange as well as OnViewChange. A host that listens only for the view change reloads nothing and shows a week filtered to the month it was already holding.

One flat gallery per view, never nested. An inner gallery cannot read the outer ThisItem, and a control reading through a container returns a frozen value. The month grid is six rows of seven cells, each cell computing its own date from the row's WeekStart.

Overflow opens a day panel, it does not grow the cell. Growing would need the row height to change and the cell to hold as many chip slots as the busiest day might ever have. The panel shows every event on the day whatever the count, with room for full titles.

Chips carry a transparent button for the tooltip. ModernText has no Tooltip, so a title truncated to the cell width would be unreadable. The overlay supplies the tooltip, the tap, and a real keyboard focus stop.

Inactive views produce no rows. Hiding a gallery stops it being laid out but does not stop its Items evaluating, so each view's Items is gated on the active view. Without that, every toggle paid for all three.

Holidays use observed dates. Independence Day on a Saturday is observed on the Friday, and the Friday is the day that gets tinted.

Colour comes from the Theme table. A timed chip is a tint of its channel colour, and the tint amount is a theme value rather than a constant, which is what keeps it legible in both modes.

Use cases

When not to use it. If you need resource columns, drag to reschedule, or overlapping events laid out side by side within an hour, this is not that component. It is a scheduling calendar, not a booking grid.

SharePoint

Two lists. Series holds the rules; Occurrences holds the rows this component reads.

Index OccurrenceDate. A Flow materialises a rolling window of occurrences from the series rules, and ExceptionType protects rows a user has edited from being regenerated over.

The full model, including why the clock is stored as text and what the three edit scopes cost you as writes, is in the recurrence contract.

After you paste

Set Width by hand. A pasted instance arrives at 600 regardless of the YAML. Height comes through intact.

Pass every Config key, including the ones left at their defaults. A Record input's Default does not reach a pasted instance.

The instance syntax is Control: CanvasComponent with a ComponentName sibling, not Control: cmpCalendarPro.

Bind Events to a windowed collection, not to a list. Binding a whole SharePoint list directly will appear to work on a small list and quietly truncate on a large one.