Pro User
  • All of Microsoft
  • My Role
    • All in My Role
    • Pro User
    • Administrator
  • Focus
    • All in Focus
    • Microsoft Ignite 2026
    • Microsoft Copilot
    • All about AI
    • M365 Admin
    • What's Hot
    • M365 Release
Timespan
explore our new search
SharePoint Lists: build interactive D3.js views with Copilot
SharePoint Online

SharePoint Lists: build interactive D3.js views with Copilot

by HubSite 365 about Daniel Anderson [MVP]

A Microsoft MVP 𝗁𝖾𝗅𝗉𝗂𝗇𝗀 develop careers, scale and 𝗀𝗋𝗈𝗐 businesses 𝖻𝗒 𝖾𝗆𝗉𝗈𝗐𝖾𝗋𝗂𝗇𝗀 everyone 𝗍𝗈 𝖺𝖼𝗁𝗂𝖾𝗏𝖾 𝗆𝗈𝗋𝖾 𝗐𝗂𝗍𝗁 𝖬𝗂𝖼𝗋𝗈𝗌𝗈𝖿𝗍 𝟥𝟨𝟧

Copilot in SharePoint can build an animated D3.js view over list data, with controls for playback, themes and department filtering.

Key insights

  • The demonstrated Request Race is a view over a SharePoint list of help desk requests.
  • Copilot in SharePoint creates the view from a prompt, then accepts follow-up requests to change it.
  • The example animates categories month by month and adds commentary about each month.
  • The finished view includes department filtering, light and dark modes, and timeline playback controls.

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.

What it does

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.

Who it is for and what you need

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.

How it works

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.

  1. Open the SharePoint list that contains the data, and start from an existing list view such as “All Requests.”
  2. Open Copilot in SharePoint and prompt it to create the desired view. The example asks for an animated request race that presents the list data by month and category.
  3. Review the first version. In the example, the bars animate through the months; the maker can replay the sequence and inspect the month labels.
  4. Ask Copilot for specific improvements. The demonstration adds a monthly commentary line and slows the animation so there is more time to read the changing information.
  5. Continue refining the presentation: add a light and dark switch, turn the commentary into a card in the upper-right area, and request that the light theme be the default with a white background.
  6. Use the finished controls to change departments, switch themes, pause or replay the animation, or move month by month on the timeline.

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.

Limitations and alternatives

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.

Sources

Frequently asked questions

What does the D3.js SharePoint list view do?

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.

How do you create a D3.js view with Copilot in SharePoint?

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.

Can users control the SharePoint Request Race animation?

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.