Forum Discussion
Linking data determined in PBI Desktop with Subsequent Power Queries?
Hi,
Please excuse and naivety in the following question - this is all a bit new to me!
I have a list of Component Part Numbers, each having a Revision against it (Rev A, Rev B, Rev C etc). There are many occasions where the same Part Numbers are repeated in the list, but with each instance accompanied by a different Revision.
I wanted to find the latest Revision for each Part Number from my list and managed to achieve this partly using Power Query (where my list originated), but mostly within the table in the Data view of PBI Desktop, adding columns and writing commands in DAX (I found that using DAX I was able to do things easily that I wasn't able to in Power Query).
However, I now have a problem. I want to use the latest Revision for each Part Number in a subsequent Query in Power Query - but the latest Revisions are determined in Power BI Desktop. Is there any way of 'linking' the Query with the result in Desktop? I am doubtful, but would appreciate confirmation from someone with greater knowledge and experience than me!
Many Thanks.
Hi Anonymous ,
Dax and M language are different.
M can be considered as a query formula language and it can be used in the Power BI Query Editor in order to prepare data before it can be loaded into the Power BI model.
On the flip side, DAX is an analytical data calculation language which can be used for in-depth data analysis during the Data View phase.
M and DAX are not dependent upon each other and follow totally different structures and logics, and have different underlying codes. M and DAX cannot be used simultaneously since the M language is used in Query Editor while DAX is mostly used in the Data View model.
Differences between the M Language and DAX in Power BI
I believe what you can do in DAX, you can do in Power Query. Without sample data and expected results, I guess that you may need the Group by feature.
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
2 Replies
davehusMemorable Member
Hi Anonymous , Have you any sanitised data that would give an idea of what it is you are trying to achieve. Even a sample PBIX file maybe?
Hi Anonymous ,
Dax and M language are different.
M can be considered as a query formula language and it can be used in the Power BI Query Editor in order to prepare data before it can be loaded into the Power BI model.
On the flip side, DAX is an analytical data calculation language which can be used for in-depth data analysis during the Data View phase.
M and DAX are not dependent upon each other and follow totally different structures and logics, and have different underlying codes. M and DAX cannot be used simultaneously since the M language is used in Query Editor while DAX is mostly used in the Data View model.
Differences between the M Language and DAX in Power BI
I believe what you can do in DAX, you can do in Power Query. Without sample data and expected results, I guess that you may need the Group by feature.
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.