#Tableau Desktop & Web Authoring162 人がディスカッション中

Hi, 

I may still not fully understand what you’re trying to achieve, but are the values shown in the Sample diagram what you’re referring to? 

For checking purposes, I’ve displayed each value as well. 

Since the processing is done with an LOD calculation, please be aware that if you need any filter operations, you’ll have to use a Context Filter. 

@Roberto Barranco technically, you should not have been able to publish the original dashboard to Tableau Public with a file size greater than 15 million rows of data, to begin with; regardless of data source type.

So, I'm not sure how that was accomplished, perhaps a fluke?  Tableau Public has had that 15M row limitation for a very long time. 

As we know, things change over the years and Tableau Public is no exception.  It's possible that when it was originally published, the version when it was published somehow allowed it to happen.  But now, with newer versioning, tighter controls are likely reinforcing the limitation better. 

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)

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 :)

You would have to create a LOD calculation and use it as a dimension filter to get the desired result. However, You should not use a hierarchy since the dimensions are fixed in the LOD calculation.