Re: we should rename some functions!

Anonymous · ‎08-25-2023

Just this morning, I'm trying to figure out how to turn a column of records into a list of nested lists... and the function turns out to be Table.ToRows. Why not rename this function to be more intuitive/easy to find? Table.ToLists , for example, is a good option. My point being, sometimes it is very difficult to find the function you need to use because the naming is just totally arbitrary.

ImkeF · ‎08-25-2023

Yes, I would go with it 🙂
But I don't think that the product team would go such a path and create a new function with the same functionality of an already exising function, tbh.
But you might want to try creating an idea for it 😉

Imke Feldmann (The BIccountant)

If you liked my solution, please give it a thumbs up. And if I did answer your question, please mark this post as a solution. Thanks!

How to integrate M-code into your solution -- How to get your questions answered quickly -- How to provide sample data -- Check out more PBI- learning resources here -- Performance Tipps for M-queries

ImkeF · ‎08-25-2023

Hi @Anonymous ,
I feel your frustration.
However, a "Table.ToLists" function wouldn't indicate whether it works vertically and chunks up into columns or horizontally splitting up into rows.

Imke Feldmann (The BIccountant)

If you liked my solution, please give it a thumbs up. And if I did answer your question, please mark this post as a solution. Thanks!

How to integrate M-code into your solution -- How to get your questions answered quickly -- How to provide sample data -- Check out more PBI- learning resources here -- Performance Tipps for M-queries