Default date in slicer

[Sibrulotte]

hi, 

i've seen a few posts about default slicer values, but none that would help in my scenario.

I have two tables, one with a list of emailing sendouts, email, and the date it was sent.

the other is a transactions table with sales per email, the date of the transaction and the amount.

Sendout:

Email, Date, Sendout_name

Transactions:

Email, Date, amount

The key is done on emails, and emails only.

I'd like to show a sum of amount, but with transaction date slicer starting at the date of the sendout.

is that possible?

[AllisonKennedy]

Is it a 1 to many relationship? You can do it if so and with a Date table that only filters the SendoutDate and does not filter or have relationship to Transactions date.

[Sibrulotte]

btw @AllisonKennedy , I'm very thankfull for the attention you brought to my post 🙂

I'm just to familiar with the solution you're refering to.

[AllisonKennedy]

@Sibrulotte please can you share here a screenshot of your model view with relationships, and also click on Manage Relationships and share a screenshot of that so I can see what columns are related between each tables. Once I see what you have done so far, I can advise how I would change it.

You should have a date table in your data model too: https://excelwithallison.blogspot.com/2020/04/dimdate-what-why-and-how.html

[Sibrulotte]

Hi, unfortunatly, it is not a one to many relation.

Envois _Qv contains many communications, and for every communication there are many recipient emails (NEP is the field in this case linking to my transactions).

And my transactions (Rentrées_de_fonds_FF) can have many transactions for the same email/NEP.

[Sibrulotte]

Too late for a follow up? 🙂

[Sibrulotte]

@AllisonKennedy  I guess many to many relationships won't allow for your solution to work?

[AllisonKennedy]

It looks like you're doing reporting on many fact tables, so you need to connect them all using Dimension tables. In your case you'll need a DimNav that has each NAV exactly once. Use that to connect the two fact tables envois and reentre.

I'm not sure how advanced your knowledge of relationships in Power BI is, but I've written these posts to help explain why many to many should be avoided: https://excelwithallison.blogspot.com/2020/08/its-complicated-relationships-in-power.html

https://excelwithallison.blogspot.com/2020/08/its-complicated-relationships-in-power_11.html

https://excelwithallison.blogspot.com/2020/08/its-complicated-relationships-in-power_92.html

You will also need a DimDate table connected to all the tables with dates.

[Sibrulotte]

it is a 1 to many relatinship.

Do you have any links to show me what you are refering to?

[Sibrulotte]

 hoping for a taker on this 🙂