There's a lesson hiding inside this assignment frustration, and it has nothing to do with pivot tables. The real problem here is that Excel treats your line chart and your filled map as two separate worlds, even though they belong on the same dashboard. The student who posted this question isn't stuck because they lack skill. They're stuck because the tool they're using forces them to jump through hoops that shouldn't exist.
A timeline filter should be a single, shared control. You build one, you connect it to every chart that needs it, and you move on. Instead, Excel demands that every chart originate from a pivot table, and then it refuses to let a filled map be built from one. That contradiction isn't the student's fault. It's a design limitation that turns a straightforward task into a research project. The student has already done the hard work, creating the charts, extracting the data, building the map. The missing piece isn't technical knowledge. It's a tool that respects the logic of a dashboard rather than the quirks of its own architecture.
What this means in practical terms is that anyone building dashboards in traditional spreadsheets will keep hitting this wall. You can learn every workaround, every manual connection, every fragile data link, and you will still spend more time fighting the tool than analyzing the data. The student's experience is a perfect example: they know what they need, they can describe it clearly, but the software won't cooperate. That's not a learning opportunity. That's a productivity tax.
The solution isn't to master Excel's pivot table limitations. It's to use a tool that treats data as a single, connected source from the start. A timeline should be a native element that any chart can reference, regardless of how that chart was built. When your line chart and your filled map share the same underlying data model, filtering by quarter becomes a single click, not a scavenger hunt through forum posts. The student's assignment is asking for something that should be simple. The only reason it isn't is because the tool was designed before dashboards were expected to work this way.