Count Data based on Filter

Pull the Sale on to a card. Change the aggregation in the Values well to Count.

OR

Create a measure like CountSale = COUNT(TableX[Sale])  and drag that on to a card

Anonymous 

If you date is connected to Date calendar you put that on any visual any of the fields from the sales table and change aggregation on the fly by right click on the field in the visualization pane

Or create like

Cnt = count(table[Cust Id])

Dis Cnt = distinctcount(table[Cust Id])

Cnt = count(table[AgentId])

Dis Cnt = distinctcount(table[Agent Id])

To get the best of the time intelligence function. Make sure you have a date calendar and it has been marked as the date in model view. Also, join it with the date column of your fact/s. Refer :
https://radacad.com/creating-calendar-table-in-power-bi-using-dax-functions
https://www.archerpoint.com/blog/Posts/creating-date-table-power-bi
https://www.sqlbi.com/articles/creating-a-simple-date-table-in-dax/

Hi Anonymous ，

Drag  column Sales of  the table to a card visual, right click the field and choose" count":

Or you can create a measure as below:

measure = CALCULATE(COUNTROWS('Table'),ALLEXCEPT('table 2','table 2'[Date]))

Then put the calendar date to a slicer :

Finally you can fulfill what you need.

Here is the related .pbix file.

Thank you for the replies.  I don't think I gave a good explanation of the issue.  I'll try and give a better explanation with some expanded data.  I have 2 tables, a readings table and a date table.  The date table is simply a list of dates.  The readings table has all of the pertinent date.  I have the 2 tables joined via the readingDate field.  I have a slicer visual that is using the Date field in the date table.  What I want to do is to count all of the Second Sale rows that fall within the slicer selection.  So based on the below data, if the slicer is set to 3/5/20-3/9/30 - I'd expect to see 3 retuned on a card visual.  Is this possible?  I tried the solutions presented and they don't seeme to working as I imagined.  Thanks!

One side note - the second sale field is actually a related measure that is coming from a customer table joined to the readings table via the customerid.