Understanding data lineage in DAX 

Just when I think I am beginning to understand a little DAX I watch one of Alberto's videos and I realize I know nothing. Bravo Alberto! Another great video.

I really do not find words to say, you are the master of DAX. Kudos

10:51 "and it's actually easier if we try to do that together" - THAT IS what I've been telling my manager all this time, bring Alberto or Marco in, DAX issues will get so much easier when working together; he said no :). Thank you, Alberto, another absolutely great video about DAX!

Every day with new and awesome videos!! Thank you so much for sharing!

Great video Alberto! Very well explained, and it opens up a lot of possibilities of doing work in a scalable way!

That's great vid, now I get what needs to be done for my PBI report.Thanks SQLBI

It's a very deep understanding, thanks for your effort !

Great learning.. Thanks much Alberto

Great to know that an expression in a table expression will break lineage, and that TREATAS can restore it. TREATAS is my best friend in a pinch :)

Now I understand TREATAS after several iterations of reading and watching

nice video! thank you!

Great, Thank you!

Yes, I am enjoying DAX...

NO CONTOSO! Great one, as usual.

Thanks for this great video Alberto! I worked through this from a time intelligence perspective wanting to try a list of Calendar month seq numbers shifted back by 1. I called this column “NewSeqNum”. As you point out, this column expression breaks lineage, and can’t be used to *define* filter context… However I am able to call these same new column values within a CALCULATE measure to *modify* filter context. Is this correct? CALCULATE([Sales], FILTER(ALL(Calendar), Calendar[Mo Seq#] = NewSeqNum))

Great Video!!! Can you kindly also explain the concept of Expanded Tables with Industrial Standard examples?

Is there a video that will present 10 rows of measures and allow the columns for monthly past totals

Great video once again! One question, why use VALUES() before certain columns?

Does the treatas applied to multiple columns in the model cause in the SE query somehow it to generate a crossjoin to be able to filter the context on the fact table? Given that, if we do the same for two big dimensions (not date as the second dimension), will it cause performance impacts?

At 11:49 , why the column name in addcolumn() is preceded with "@" e.g. "@FirstSale"? Thanks.

Hello Alberto, one question : when you used TREATAS with the BrandNewNameCorrectLineage, " *NO CONTOSO* " disappeared from the final query results. My question is : the row is not visible because the measure [Amt] for that Brand was BLANK.... or the row is not visible because TREATAS itself removed it from the BrandNewNameCorrectLineage variable as it's not an existing Brand ? My answer would be the first one.... Thanks Alberto

Cio Alberto! Amazing Video! DAX Training courses are online? I mean, not recorded videos, that we can interact with you during the training or we have the both options? I am located in Germany. Thanks!

How can we set the data lineage if the table variable has more than one column i.e how to reference that column of table veritable to be treated as a column from the original table.

Are there any ways in DAX(Studio) to *explicitly* examine the data lineage of a column? To me, it seems that the didactic problem is that lineage is very much hidden from the user and any way to make it visible would help.

Hard for me.

Mr. Ferrari, he did not know how to explain the causes that break the lineage. It is a pity so many years of experience and he did not know how to transmit it. that was the important thing about this video, restoring it is the least. but what really breaks it?