This morning, I wasn't at my work computer so I didn't have access to the code. Here is the literal code I used:

Combined Units:=IF(

ISFILTERED(DimDate[WeekOfMonth]) || ISFILTERED(DimDate[WeekOfQuarter])...

I did this recently for a hierarchy showing a different measure at each level. For what I did, I used a combination of "IF" and "ISFILTERED". There are other related...

Try "dd/MM/yyyy". Lower case "m" is minute. Other than that your string looks correct to me.

This page has the codes. User defined dates are almost at the bottom.

https://msdn.microsoft.com/en-us/library/microsoft.visualbasic.strings.format(v=vs.110).aspx

I'm not sure if you're using Multi-dimensional or Tabular. For multi-dimensional, there is a format_string property. I don't recall what it's called in the GUI but it should be obvoius....

For this, you'd be better to work this out in the ETL and create a snapshot fact table. Over time, you'll always have to cover all the historical sales data...

You have a tie on the Start Date. The Tail function is pulling a list of EmployeeID and the latest start date. Then it's joining to the rest of the...

Here is a query that will get the results you're looking for. I don't have your data model, but this works with a basic cube I created. Hope this helps.

SELECT...

The issue has to do with your MIN/MAX formulas. They are providing the value at that intersection of dimensions. I had this issue recently in tabular but can't remember right...

What happens if you remove the Units column? Does it still return all the batches? Also, is this MD or Tabular?

SSAS Tabular does not support many-to-many relationships natively. You'll need to write DAX. The most concise, easy to understnad article I have found on this topic is: https://www.sqlbi.com/articles/optimize-many-to-many-calculation-in-dax-with-summarize-and-cross-table-filtering/.

Good job. Glad to help.

One more thing, are you formatting the parameters to look like the members? I would recommend a trace at this point so you can see the raw MDX.

I suspect the problem is with the Lag(@LagMonths) but I'm not sure. Can you try putting a constant in there to see if that's the problem?

Another troubleshooting tip is to...

Try the StrToMember function. Also make sure your parameter strings are formatted correctly. Here's a snippet of code I used that is working.

{StrToMember(@MonthYear, CONSTRAINED).lag(23):StrToMember(@MonthYear, CONSTRAINED)}

I would try running a server-side trace with SQL Profiler. You may be able to spot some other difference you didn't know was there.