In the 44th session of Chandoo.org podcast, let’s talk about failures.
What is in this session?
In this podcast,
- Book announcement about Dashboards for Excel
- Story of my first ever dashboard
- Important lessons – Requirement Analysis for dashboards
- Resources for creating awesome dashboards
- Podcasts
- Books
- Courses
Listen to this session
Podcast: Play in new window | Download
Subscribe: RSS
Click here to download the MP3 file.
Resources to make awesome dashboards
Podcast episodes:
- Create awesome dashboards with this 10 step process
- Make better charts by optimizing Data to Ink ratio
- Rules for making legendary column charts
Books on Dashboards:
- Information dashboard design by Stephen Few
- Non-designers design book by Robin Williams
- Dashboards for Excel by Jordan & Chandoo
Courses:
- Excel School + Dashboards – Online classes from Chandoo
Excel School, is a comprehensive online course to help you become awesome in all aspects of data analysis, visualization, interactive workbooks, dashboard reporting and automation.
In this course, you will learn to:
- Analyze data using simple & advanced formulas in Excel
- Structure & process large volumes of data quickly using tables & pivot tables
- Present information using charts, interactive & dynamic charts and complex charts
- Create dashboards using 8 in-depth tutorials & case studies
- Make gorgeous workbooks using conditional formatting, color & font choices and more
- Develop workbooks faster: using my favorite tricks and productivity hacks
Please click here to know more about Excel School and enroll
Transcript of this session:
Download this podcast transcript [PDF]
Help our community & me learn more by sharing your mistakes
It’s your turn. Share the mistakes you made during data analysis, dashboard preparation or automation projects. Let’s all learn from these and become stronger.
10 Responses to “Multiple Find Replace with Power Query List.Accumulate()”
Note: The text-formula above miss a -1. The video is correct.
😀 sorry, I made the exact same mistake as you did - initially - in the video. {0..3} is one thing, and Table.RowCount(replacements) -->3 items ={0,1,2} is another thing.
1st question : you've created a new column to put the replacements in. how ca we replace in the original column without creating a new one ?
2nd question : how can we replace the value in the entire cell and not only the text (Using ReplaceValue instead of text.Replace) ?
Thanks you in advance
Chandoo, I would be very interested to have your answers in both Yassine's questions!
Thank you for sharing,
Vassilis
Thank you for this! I was just doing an assignment where I was having to replace words with other words in my Excel sheet. We are starting with the basics in my class, so I know I don't have a huge list that I would need to find and replace, but this is something that could be useful down the road for me!
Hi
This is nearly perfect for my needs thank you, however I would like just the "replace" to be the result if possible please, I have tried in vain adjusting the formula without success.
Thank you in advance
Thank you! Awesome tip, and very flexible, too.
My find/replace values were in non-adjacent columns of a table containing a bunch of other data. Worked prefectly and I am now a tiny bit less clueless.
Hi!!!
I have the same question that Yassine did.
I need to replace the values in the same column. I don't want to create a new column e then have to remove the old column.
How could I could that?
That's a real fun article. It inspired me to delve deeper into the topic of List.Accumulate. I can see how the function works, but it takes an additional step to imagine how one can use it for more complex applications.
Your example also made it into my article, together with some other use-cases. Would be great to get your opinion on which other areas you would include in the article.
Let me drop the link to the page so others can too find it for further reading: https://gorilla.bi/power-query/list-accumulate/
Expression.Error: The name 'replacements' wasn't recognized. Make sure it's spelled correctly.