#Tableau Pulse11 utenti parlano di questo argomento

@Alex Rogers Pulse can take a custom calendar, including a 53-week one. It will not do that shifting week-1-versus-week-2 comparison by itself.

The calendar has to live in the data source, with the calendar fields in the same table, related to the sales data if they sit apart. Each date needs a day of year, week of year, month of year, and quarter of year. Those numbers start at 1 and step by 1, with no gaps. A week is 7 days. If week 53 is short, week 1 of the next year has to finish that 7-day week. Pulse checks this when you set the calendar on the metric, and it shows the first error it hits.

Fiscal year start on the data source is the simpler case. A Monday that moves every year, plus a mix of 52 and 53 week years, is the custom calendar table, not Fiscal Year Start.

Comparing current weeks 1-52 with last year's weeks 2-53, or double-counting week 1 when the lengths flip, is not a built-in Pulse comparison. Pulse compares periods on the calendar you gave it. If the comparison date is not the same week number last year, put that comparison date on the row. Zeroing out-of-period days is why the line still starts in January.

Hi Himshikha, happy to help! Yes, Pulse can do Rep-level self-service, but through adjustable metric filters on the metric page, not a custom homepage, so your understanding there is right. 

1. On the metric definition, add your Rep field as an adjustable metric filter (in Create/Edit Metric). Once it is there, any user can filter that metric to a specific Rep directly on the metric page and change it themselves, that is the granular self-service filter the client wants. Keep it within the first 20 adjustable filter fields, because those are also what drive the breakdowns and the AI insights. 

2. When a user applies a filter, Pulse creates a filtered version of that metric for them, and their filter and time selections are preserved on their own Pulse home and in their digest. So each Rep effectively builds their personalized view by following the metric and setting the filter, rather than you building a per-user homepage. 

3. Tie it to the RLS you already set up: the Virtual Connection data policy scopes each user to their own rows automatically, so a Rep only ever sees their data even before touching a filter. The adjustable filter and breakdown then let them slice within that. Together that gives real Rep-level self-service. 

You are right that there is no free-form custom homepage builder in Pulse, that is by design, it is metric-definition driven. If the client genuinely needs an ad-hoc build-your-own filtered page, that is a Tableau viz or dashboard use case, not Pulse. 

if this helps, please mark it as the Best Answer so it helps the next person, thanks 🙂

@Himshikha Purohit

Hi, the best idea could be to use the Tableau Pulse object in a Tableau Workbook Dashboard. 

I exactly don't remember if it was 2025.3 or 2026.1 when Tableau introduced the capability of Dashboard filter controls (not Filter Actions) can affect Pulse Metrics. 

Thus: 

a. Create a workbook in Tableau Cloud (Explore -> New Workbook) 

b. Connect to the published datasource your metrics use. 

c. Create a simple sheet and drag filters to the filter shelf. Show filters. 

d. Create a Dashboard, and drag your sheet. 

e. Drag Tableau Pulse objects to bring your metrics into the Dashboard.  Don't forget to  toggle on "Respond to filter selection"  

f. Publish your workbook. Your metrics will respond to the filter selections. 

For more info, you may take a look of: 

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you. 

Regards, 

Diego Martinez 

Tableau Visionary and Tableau Ambassador 

Hi Monika,

Sometimes when you convert from normal view to mobile view the filters will only operate on the original normal view - I've never done enough research into the specific reason why this happens but you can confirm this by using the filter and switching back to the normal view - it should have applied on that screen, but doesn't on the mobile view.

To get around this, just delete the filter, then in the mobile view re-expose the filter which you know will apply to that sheet, and it will work just like the original should have. Technically this is 2 separate filters, but I doubt your usecase will have users that dynamically switch between mobile and desktop views (its a very rare event and F5 refresh will fix it).

HTH

Peter

 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.

Hi, @Berlene Tamayo

This isn’t exactly the same request, but there is already an Idea related to Pulse’s period/granularity. If you’d like, please consider giving it an upvote. 

<Existing ideas> 

https://ideas.salesforce.com/s/idea/a0BHp000017JjOtMAK/defined-aggregationperiods-for-pulse-metrics

I’m looking forward to seeing how Tableau Pulse evolves in the future. :)

Hi, 

Are you looking for something like the attachment? Please take a look. 

The idea is to create parameters with ON/OFF values and then set up corresponding fields that switch OFF/ON in response, allowing you to control visibility through parameter actions. A dedicated sheet is prepared for the checkbox, where ON and OFF are represented using shapes. Please see the details below. 

This was implemented using only standard features. The display switching is handled by configuring a DZV. 

<sample>

 <parameter>

<calc>

<dashboard action>

 <check box sheet settings> 

Using the “off‑on” field from the checkbox sheet, the display switching is achieved through a parameter action. 

-Configuration for the checked state. Please pay attention to the shape and color.

*Sorry if the square shape is a bit confusing, but the checkbox frame itself is represented using borders.”

-Configuration for the unchecked state. Please pay attention to the shape and color.

<Dashboard DZV settings>

@Himshikha Purohit

I don't think that would be possible. My best suggestion would be for you to create an idea (

)  

Something like a check box -> "null values to zero when missing values" 

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you. 

Regards, 

Diego Martinez 

Tableau Visionary and Tableau Ambassador