A Microsoft MVP 𝗁𝖾𝗅𝗉𝗂𝗇𝗀 develop careers, scale and 𝗀𝗋𝗈𝗐 businesses 𝖻𝗒 𝖾𝗆𝗉𝗈𝗐𝖾𝗋𝗂𝗇𝗀 everyone 𝗍𝗈 𝖺𝖼𝗁𝗂𝖾𝗏𝖾 𝗆𝗈𝗋𝖾 𝗐𝗂𝗍𝗁 𝖬𝗂𝖼𝗋𝗈𝗌𝗈𝖿𝗍 𝟥𝟨𝟧
Copilot in SharePoint can build an animated D3.js visualization over SharePoint list data, turning a list view into an interactive way to follow changes over time. This approach is relevant to SharePoint users and makers who want to present list information as a visual story rather than only as rows and columns. Daniel Anderson [MVP] demonstrates the workflow by building a request-race view for help desk requests.
The example, called Request Race, displays categories of help desk requests changing month by month in an animated bar chart. The chart is presented as another view on the list, alongside existing views such as “By category” and “Open requests.” The underlying example data remains in the list; the visualization gives users another way to look at it.
D3.js is used here to create the visual experience, while Copilot in SharePoint is the way the maker asks for the view and makes changes. The initial prompt produces a first version. Follow-up prompts add or adjust details, including monthly commentary, the pace of the animation, a theme switch and the placement of commentary in a card.
The final example offers more than a moving chart. Users can switch between departments or view all departments, change between light and dark themes, pause or replay the animation, and move through months on a timeline. Monthly commentary appears in a prominent card as the chart progresses.
This workflow is aimed at people who work with SharePoint lists and want a more tailored presentation of their data. It may be useful when an audience needs to see how categories change over time, rather than scan a list or select individual records. The demonstrated list contains help desk request data, but the concept is to visualize information held in a list.
The starting point in the demonstration is a SharePoint list with data and an existing “All Requests” view. Copilot in SharePoint is opened from within the SharePoint experience, and the maker supplies a prompt describing the desired visualization. The example is built interactively, with additional prompts used to refine the result.
The video demonstrates this workflow in a SharePoint sandbox. It does not present a separate development or deployment process: the interaction shown is prompting Copilot and reviewing the resulting list view. Treat the described capabilities as the demonstrated experience, rather than assuming that every list or tenant has the same setup.
The process is iterative: start with a visual goal, ask Copilot to build it, then inspect the result and request focused changes. Anderson describes the initial generation as taking roughly 90 seconds to two minutes in his demonstration. That is an observation about the example, not a general performance measure.
This pattern makes the prompt-and-review cycle central to the work. Rather than treating the first output as final, the maker checks whether the chart, pace, commentary and controls serve the intended audience, then asks for adjustments. The example’s controls also illustrate why the visual needs to be considered as an experience: viewers need ways to follow the data at their own pace and focus on a department.
The demonstration uses sample data created for the example, so its request counts and month-by-month story should not be read as real service-desk findings. A visualization is only as meaningful as the list data and the way the categories and dates are represented. Before adapting this kind of view, consider which fields and comparisons your audience needs to understand.
The example is one customized visual view, not a replacement for every way of working with a list. Its value is the animated presentation and interactive controls; the list itself remains available, as do the other views shown in the demonstration. Keep those familiar views in mind for people who need to inspect list records directly.
The workflow depends on describing the desired result clearly and then reviewing what Copilot builds. A maker should check that the visual tells the intended story, that commentary corresponds to the displayed months, and that controls behave as expected. The demonstration does not establish that every chart style or customization will be produced from a prompt.
The demonstrated Request Race animates help desk request categories month by month and displays commentary. It also offers department filtering, theme switching and timeline controls.
Open Copilot in SharePoint from the list and prompt it to build the desired view. Review the result, then use follow-up prompts to refine the animation, commentary, theme and layout.
In the demonstrated view, users can pause or replay the animation and move through months on a timeline. They can also change departments and switch between light and dark themes.