Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
samdthompson
Memorable Member
Memorable Member

Using table as a feed for a new query

Hello, I have some data loaded in power query which I have shaped and fed back to a table in powerBI. Once there I have applied some DAX. I now want to use that table as a datasource to feed it back to power query and do a final transformation. Is that possible?

 

Before you ask, yes the DAX transformations need to be done as the power query alternative was way too slow (Creating a ragged heirarchy) and the DAX is not able to unpivot the result in the way I want in an efficient way.

 

// if this is a solution please mark as such. Kudos always appreciated.
1 ACCEPTED SOLUTION
samdthompson
Memorable Member
Memorable Member

Yeah, this workss nicely. Good thinking. 

 

the why is that my ragged hirarchy has a top level of 2500+ with a near exponential rate through 12 generations but still growing. I tried using a power query function but it cycled through one record at a time. I tried using DAX to do a calculated table of what i wanted to do but the calulation time was although much faster, still too slow. Using power query to split and unpivot DAX results based on =PATH & =PATHITEM is about 22 time faster than the calculated table method and literally 100's of time faster than the custom function method.

 

// if this is a solution please mark as such. Kudos always appreciated.

View solution in original post

3 REPLIES 3
samdthompson
Memorable Member
Memorable Member

Yeah, this workss nicely. Good thinking. 

 

the why is that my ragged hirarchy has a top level of 2500+ with a near exponential rate through 12 generations but still growing. I tried using a power query function but it cycled through one record at a time. I tried using DAX to do a calculated table of what i wanted to do but the calulation time was although much faster, still too slow. Using power query to split and unpivot DAX results based on =PATH & =PATHITEM is about 22 time faster than the calculated table method and literally 100's of time faster than the custom function method.

 

// if this is a solution please mark as such. Kudos always appreciated.

Hi  @samdthompson ,

 

Thanks for your additional clarification, indeed, there are pros and cons to dax and power query.

Could you pls mark your reply as answered to let more people find the solution?

 

Best Regards,
Kelly

Did I answer your question? Mark my reply as a solution!

lbendlin
Super User
Super User

@samdthompson   (putting aside the urge to say "Why?" )

 

Once you have published the Power BI file to a workspace (and thus created a dataset)  you can then connect to that dataset from Power Query.

Helpful resources

Announcements
July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.

Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.