#Tableau Pulse18 diskutieren mit

Hello, 

Our company uses a reporting calendar which starts on different dates each year (although always on a Monday); also, although most years have 52 weeks / 364 days, there are occasionally 53 weeks / 371 days in a year. 

In our database, we have two date-related tables, the first one maps each calendar date to a reporting period (day, week, month, quarter, year): 

The second one maps each calendar date to the corresponding reporting period's start and end date, including the dates for the year-on-year comparisons: 

Combining both tables into one shouldn't be a problem, but once done, I am not sure how to configure the custom calendar in Pulse so that data can be displayed correctly. 

The above date logic has already been incorporated into a view for the sales data, however in the Tableau dashboards, I have created custom calculations with parameters in order to show the sales - the problem is this just sets values outside of the reporting period to zero, meaning when I do the same in Pulse, the graph will start from the 1st of January, but the first of January until the start of the reporting year will just be a line with zero data, and then the last 3 or so months of the reporting year will get missed (since they are in the next calendar year). 

The main questions are: 

1. Does Tableau Pulse support a reporting calendar of varying lengths? When CY is 52 weeks, and LY was 53 weeks, the YoY comparison would be CY 1-52 vs LY 2-53; when CY is 53 weeks, and LY was 52 weeks, the YoY comparison would be CY 1-53 vs LY 1-52 + CY 1 (so week 1 gets double counted). So, it's not always just a simple comparison of Week 1 with Week 1 of prior year. 

2. Does Tableau Pulse support reporting calendars which start on different dates each year, e.g. 2026-03-30 vs 2025-03-31? 

If yes to both, how do I configure it so Tableau Pulse knows which date ranges to use? The key is that there is always a 364 day difference between CY and LY comparisons. 

Hello, our time series adjustment's minimum time granularity settings for our pulse metrics are currently configured to "Month". However, the day of the month displayed in the dates leads to confusion for our users since we don't actually follow calendar days and only track our data monthly. (For example, FYTD is from Oct 4 to Jul 31, last month is May 30 to June 3

). Is there a way to remove the day in the dates displayed both in the metric cards and filters, as highlighted below? Or any alternative techniques for the dates to reflect properly?  

Filters:

1 Year in Months Sample:

Note that in our use case, custom calendar doesn't work out because the data is already aggregated monthly and configured by monthly fiscal calendar in the data source level (retracking this back to daily calendar days isn't ideal). Setting it up again using the custom calendar feature will offset the dates every period and lead to invalid numbers. Hence, we only setup the fiscal start using Desktop and publish/use that as the data source. 

#Tableau Pulse

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.

I am working with Tableau Pulse metrics and trying to understand how the Expected Range and Forecast Confidence Range are calculated behind the scenes. In my Pulse metric trend chart. 

As shown in the attached screenshot, on May 10, 2026, the metric value is 1.19M and Tableau Pulse mentions that it is within the expected range of 1.08M to 1.49M considering seasonal patterns. Similarly, the forecast for May 2026 is displayed along with a forecast confidence range. In this example, I have applied a Month-to-Date (MTD) filter as well 

When I hover over the information icon, it says: 

“The range that the metric value is expected to fall in, calculated based on the 200 data points…” 

 I would like to understand technically: 

·         How exactly is the Expected Range calculated in Tableau Pulse? 

·         What statistical or forecasting model is being used behind the scenes? 

·         Can this same logic be replicated in Tableau Desktop using calculated fields or forecasting features? 

I have attached a screenshot for reference. Any documentation or technical explanation would be very helpful. 

Thanks in advance!