Birthdays and Anniversaries FAQ and Troubleshooting
Answers to common Zenpo Birthdays and Anniversaries questions, including who appears and why action buttons can be missing.
Where do the birthday and anniversary dates come from?
From SharePoint data you choose. The Dates come from setting offers two modes: The People list (recommended), where Birthday and/or Hire date columns sit on the People list itself, or A separate dates list, where the dates live in a second SharePoint list joined to the People list by a Lookup item ID or a text key such as PersonID.
Is an employee's age or birth year ever shown?
No. Birthdays display month and day only. Birth year is not displayed or used to calculate age, and age is never shown, in either data mode.
Who appears, and who does not?
A person appears when the mapped date field contains a value. An empty cell never renders. In separate-list mode, a matching row supplies that person's dates, and rows that do not resolve to a person are not rendered. People marked with the optional External marker are excluded unless Include external people is turned on.
How far ahead does it look?
The Lookahead setting offers 7 days, 14 days (the default) or 31 days. The window includes today and the last day, and it wraps across month and year boundaries, so a 4 January birthday appears in a late-December window. Results group into Today, This week and This month. Empty groups do not render.
What happens to a 29 February birthday?
It is celebrated on 28 February in non-leap years. A 29 February hire date is treated differently by design: it produces no anniversary in non-leap years.
Why are the Send wishes and Chat buttons missing?
Those actions require the optional Email role to be mapped and that person to have an email value. Without both, no action buttons render for them.
What does the "{N} not shown" chip mean?
It is an authoring aid, visible only to an editor while that web part's property pane is open. It lists people held back: external people excluded by design, join rows that do not resolve, and rows missing data. It never appears on the published page.
The roster has more than 5,000 people
The roster cap is 5,000. The web part refuses an over-cap source instead of dropping rows. The message is This roster contains more than 5000 people. Refine the source or use a smaller organizational scope.
Shared list errors
Access, missing-list, throttling, view-threshold, timeout, and unknown-load messages are shared across list-bound parts. This product's retry button is Retry. See Common Error Messages.