The Data Modeling for Power BI training is now available as a video recorded course, including exercises!Take advantage of the launch offer until April 17, 2018.Read more about this:Why Data Modeling is important in Power BIThe new Data Modeling for Power BI courseData Modeling training guide

I recently published a new blog post on SQLBI. You can read it at this link: https://www.sqlbi.com/articles/capturing-power-bi-queries-using-dax-studio/.

The -1 is there to make sure there is no value that satisfy the filter (there are no negative quantity values), and the result of the filter is an empty table.

The measure should work, assuming the Date table is marked as a date table. Otherwise you can write: Cumulative Quantity := CALCULATE (   SUM ( Transactions[Quantity] ),   FILTER (       ALL ( 'Date' ),       'Date'[Date] <= MAX ( 'Date'[Date] )   ) ) However, this approach doesn't work ...

@Chaitanya: you might try counting the days, e.g.: IF ( COUNTROWS ( 'Date' ) <= 31, <your current MTD> ) @Francisco: I didn't understand your question!

Not sure I understand - do you want to compare the contento of the string, or the content of each column? For the former you have to manipulate the string and extract what you need, for the latter you need something like COUNTROWS ( FILTER ( table, table[c1] = table[c2] ) )

Look at these posts: https://www.sqlbi.com/blog/marco/2012/01/05/use-parameters-in-your-dax-queries/ https://www.sqlbi.com/blog/marco/2014/05/21/write-dax-queries-in-report-builder-ssrs-dax-ssas-tabular/

Which version and compatibility level are you using? If you don't have the -- MDX Script -- tag in your BIM file, you are likely using a compatibility level 1200 or higher, where this technique is no longer available (and keep in mind it's officially unsupported in any case).

Yes, but it would be a nightmare in performance... if you use Power BI I suggest you saving in a variable the MAX from one fact table and use it as a limit for the target fact table.

You can see an example here: https://www.daxpatterns.com/parameter-table/ However, I suggest you to *not* use that technique and wait that MS implements in DAX something better. The problem is performance.