Tableau Feed

Hi Himshikha - good news that it works for you and your colleagues; that tells us the RLS logic itself is sound and it is now down to just that one user. When a single follower sees blank/error while everyone else is fine, it is almost always one of two things - and the blank-vs-error distinction tells you which: 

1) An ERROR (red banner / cannot load the metric) is usually a data source PERMISSION issue, not RLS at all. This is the number-one gotcha: adding someone as a Pulse follower does NOT grant them access to the published data source the metric is built on. That one rep needs at least View (and typically Connect) permission on the underlying published data source, plus a site role that allows it (a licensed Viewer/Explorer, not Unlicensed). Grant her access to the data source and the error should clear. 

2) A truly BLANK metric (loads fine, just no numbers) is an RLS entitlement MISMATCH - her Tableau identity does not exactly match the value your user filter compares against. USERNAME() returns her Tableau Cloud sign-in identity (usually the full email), and the match is exact and case-sensitive. So if your Territory Owner / entitlement value is her display name, an old email, a different domain, or has a stray space or different capitalization, the filter returns zero rows for her - blank. Her name showing in Tableau is not enough; the value in the DATA has to equal her USERNAME() character-for-character. 

Fast way to tell them apart and pinpoint it: open the published data source (or the workbook) as the owner, drop USERNAME() and your Territory Owner field side by side on a sheet, then use the 'View As / filter as user' option to impersonate her. You will immediately see whether her USERNAME() finds a matching row (a data/mapping problem = blank) or whether it throws a permission error (an access problem). That one check usually settles which of the two it is. 

Diego's advanced-definition idea is good as well, but that is a newer Pulse capability still rolling out - your data-source user-filter approach is the right one to get working now. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

There's a method with Best Answer here:  

If this response answered your question, please mark it as an Accepted Answer? 

This way, others searching for similar solutions will find the answer faster in the future.

Best, Don Wise (Tableau Ambassador)

@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 

@Krzysztof Wascinski

Hi, unfortunatelly not possible with local auth, you will need to use an external Idp (SAML). 

I suggest you to create an idea for this: 

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 @Hideaki Shiihara

I created asn example workbook using desktop 2026.2.2 that I attached. It mimics my logic with 3 crosstabs, and a filter that changes the number of rows, and I was able to find something quite interesting: 

In the workbook I have created a box in the upper right corner so it is easier to see where the right edge of the crosstab should be. There is plenty of room for a scroll bar to open to the right of this. 

Filtering is on discount just to get some way to change the number of rows. 

If I set the lower limit to 11, everything shows OK with scrollbars appearing to the right, and the crosstab keeping its position 

If I set the lower limit to 82, the scrollbar is removed and the right border of the crosstab moves to the right => this is the issue I have in my workbook 

If I set the lower limit to 128, the crosstabs are again in their correct position??? 

I have also opened a case with Tableau for this as this seems to be a regression bug

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