Do you even need to use Power Query Functions?

You can do amazing things in Power Query! Maybe you think to create a function. But do you really need a function for that? Or is it over complicating things?


*******************

Want to take your Power BI skills to the next level? We have training courses available to help you with your journey.


*******************
LET'S CONNECT!
*******************


***Gear***

#PowerBI #PowerQuery #GuyInACube

[ItsNotAboutTheCell]

"Love the Intellisense" - I busted up laughing at that part.

[benhalicki]

If the block of code is complex enough, has a specific purpose and likely to be reused, then yeah a function is a good idea.

[rustedrootbeer]

In this case, I'd avoid the function to just keep the Advanced Editor clean. Date.From() is a lot easier than having to click on a function someone made, and understand what it's doing.

[matthiask]

I always wondered why so many users use functions though they could just include it in the query.

[TitusRex]

If the function already exists then you don't need to create a new one.

[MrSparkefrostie]

I think you have answered a question I was going to have when I start configuring incremental refresh

[joevahling]

I find setting the type when the default sets as any, saves me from having to add another PQ step of setting the type later.

[punit]

Using inbuilt functions of PQ keeps the query versatile.

I ask two questions before deciding on using a function :
Does PQ has an inbuilt function or functions for the purpose?
How much cleanliness /readability the function provides?

[lalalf]

I often use these functions when i create calendar table in PQ

[AMS]

I have needed to create a recursive function to resolve a problem within a parent-child hierarchy for a client

[GaryOJ]

This isn’t directly related but I really need help.

I’ve worked with HANA in Power BI for years now and never ran into an issue editing the SQL, by double clicking the first “applied step” and changing the sql in the box that opens.

But now, HANA Advanced SQL statement being changed to NativeQuery and I’m unable to edit SQL directly from double cliking in the query editor. They’re re-directing me to the ADVANCED EDITOR which is an insanely long, complex, one-lined code…

Is there a way to go back to the normal way? With the gear icon in the applied steps? I tried going back to an earlier version of PBIDesktop but no help. :(

[TheRahuligan]

I recently used a function to allow me to iterate through a column of values and pass them as parameters to a REST API call. Figured it'd save me writing multiple queries that are 99% the same (and allows me to keep it dynamic should the list of values I'm querying change!), but I kept running into a Formula.Firewall issue in PowerBI service when attempting to set up scheduled refresh. There was no good way to "rebuild the data combination", as at some point I need to pass the values in as parameters and make the API call, so I was stuck! Anyone else run into this issue?