Forum Discussion
AS AT slicers
Hi Steve_M
As mentioned in my previous reply, filters coming from a related table will affect what records are visible. So if you select 28/11, you will see only the 28/11 rows. Functions such as ALL, ALLSELECTED, REMOVEFILTERS etc affect the results of a measure but cannot unhide the non-selected rows. Change your slicer to before if you want to also show rows with dates prior to the currently selected.
Super UserHi Steve_M
The simplest method for transactions not to be fitlered out is to use "before" slicer and cover the start date with a shape. If you are using a live connection and there isn't a disconnected dates table in the model, you'll be limited to this. You will have more flexbility with connecting to a semantic model via direct query (if enabled). While you can use measures to modify the filter context and show values outside the selected range, a related dates table will show only the rows that's been selected.
Here's the demo- https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Accounts-Receivable-Aging-Schedule/td-p/3960847
Sample pbix and tutorial on YouTube.