RLS vs Filter for current user

jdbusselman: I found this post while looking for a solution to the very same problem. I couldn't find a solution elsewhere so I tried myself and I think I found a usable workaround to achieve the desired result without having to use RLS.

1. Create a table to use as a filter later on: "Filter Table" with one column, two values: "yes" and "no". I did it with M:

   let
       Source = Table.FromRows(Json.Document(Binary.Decompress(Binary.FromText("i45WikwtVorViVbyy1eKjQUA", BinaryEncoding.Base64), Compression.Deflate)), let _t = ((type text) meta [Serialized.Text = true]) in type table [Choice = _t]),
       #"Changed Type" = Table.TransformColumnTypes(Source,{{"Choice", type text}}),
       #"Renamed Columns" = Table.RenameColumns(#"Changed Type",{{"Choice", "Show only my stuff?"}})
   in
       #"Renamed Columns"

2. Create a Measure that filters data using username():

   # my stuff = CALCULATE(
       COUNTROWS('AllStuffTable');
       FILTER(
           ALL('AllStuffTable'[UserName]);
           'AllStuffTable'[UserName] = username()
   ) 

3. Create a Measure that chooses the measure above when the value "yes" is selected in the "Filter Table", otherwise show unfiltered data:
   

   # stuff = 
   SWITCH (
       SELECTEDVALUE ( 'Filter Table'[Show only my stuff?] );
       "yes"; [# my stuff)];
       COUNTROWS ( 'AllStuffTable')
   )

4. Create a data table with all desired fields an add the "# stuff" measure. By default, tables don't show rows where all measures are BLANK. We can use that, because for data that is not "my stuff" the measure "# stuff" will be BLANK and therefore excluded from the table.
5. When filtering the "Filter Table" to "yes" or "no" you will see a filtered result in the data table or not. You could put the filter in the filter pane or as a slicer on the canvas for user to switch to "their stuff" an back.

Does that make sense?