Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Just check a rank that can be created on the date within the customer. That will give you the order and based on that you can calculate your next or previous date.
https://radacad.com/how-to-use-rankx-in-dax-part-2-of-3-calculated-measures
https://radacad.com/how-to-use-rankx-in-dax-part-3-of-3-the-finale
Hi -
Thanks for replying. I'm not getting it. The biggest thing I'm not understanding is how would you limit sales transactions to only those of a specified customer without filtering?
Secondarily and far less important, if I rank sales transactions based on date, the first one would be ranked 1, the second one would be 2, etc. Whether the second one happened within 90 days won't be reflected in a ranking...
I'm confused! 🙂
Redacted
Did this solution work for you?
@thatnerdguy I would approach this in a completely different way now than I did four years ago.
Good luck with the interview! 😉
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 43 | |
| 39 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 68 | |
| 63 | |
| 31 | |
| 30 | |
| 23 |