We're actively looking for ideas on how to improve Weekly Challenges and would love to hear what you think!Submit Feedback
My solution attached. Had fun doing this in between other tasks and adding some customization to the interface. Only thing I would mention is that the solution data has populated some secondary type values where they didn't exist in the original dataset - maybe something to adjust there.
Fun challenge, love Pokemon 😄 video solution here: https://www.youtube.com/watch?v=ACsTFXrxRaY&list=PL18SpOXDj-KMUD4YwWC5vZaUsIa7drxNZ&index=20&t=0s
Q is like a "Question" that can be connected to a tool that has an expression builder. So tools like formula, filter etc will have the Q attached to it.
When you connect the 2 Q's the actual expression or 'question' gets passed onto the workflow and not the selected or resulting data. For example, if you had a filter tool in your workflow and were filtering for a value 'Legendary', you could run the workflow and get results with 'Legendary' in it. However, when you connect the Q's, the expression for filtering gets added to the workflow and you cant run the workflow anymore to get the same results as before. Hence, de-bugging becomes harder. If you were to instead connect to the lightening bolt, you could still run the workflow and get the results as before. This is one of the major advantages of connecting to the lightening bolt.