Hi all,
I'm in the process of setting up a custom financial calendar for use in Tableau Pulse and running into a specific issue when trying to apply it to a metric.
I’ve built a calendar table that follows Tableau’s documented requirements for Pulse custom calendars. The financial year starts on 1 March, and the table includes all required fields: "Reference date", "Day of year", "Week of year", "Month of year", "Month name", "Quarter", and "Year". The calendar spans from March 2021 through February 2025, with every single day represented and no missing values. All fields are within the same table.
I’m using the Sample Superstore dataset to test this. I’ve created a relationship between "Reference date" in the calendar and "Order Date" in the Superstore data.
In the Pulse metric builder, the custom calendar fields appear correctly, and I’m able to select them when setting the calendar for the metric. However, when I click "Apply", I get a 400 Bad Request error. The configuration fails at that point and the calendar isn’t applied.
Despite this failure, I can still proceed to build the metric — but only by continuing without the custom calendar. This highlights that the calendar itself is the issue, not the metric logic or data structure. Pulse allows the metric to be built, but not with the custom calendar attached.
I’ve double-checked that:
- All required fields are present and properly typed
- Every day is included across all years, with no gaps or duplicates
- No filters are applied to the calendar table
- The relationship between calendar and fact data is recognised and working in Tableau Desktop
If anyone has successfully applied a custom calendar in Tableau Pulse without encountering this issue, I’d really appreciate hearing how that was achieved.
hi,
The setup sounds correct. Since the calendar fields are visible in Pulse but Apply returns 400, I’d suspect an issue with how Pulse is validating the calendar relationship rather than the calendar fields themselves.
One thing I’d check is whether the calendar table is configured as a proper date scaffold with a 1-to-many relationship from Calendar → Superstore, with Reference date as a true Date field on both sides.
Also try testing with a shorter calendar range that fully covers the Superstore Order Date range, then apply the custom calendar again.
If the same 400 error persists, I’d check the Pulse/ Tableau Cloud version and error details in the browser/network logs, as this could be a Pulse custom-calendar validation issue rather than a Desktop relationship issue.
