Power BI: Feedback via Lists & Forms

Key insights

• Core approach: Store feedback in a SharePoint List or Dataverse table, capture input with a form or Power Apps, and surface those entries in Power BI.
  This separates comment capture from reporting so Power BI shows data while the list/table holds text, author, and timestamps.
• Why it matters: You get a stable Microsoft-only workflow that supports security, auditing, and治理.
  This is easier to govern than ad hoc email or Excel feedback and fits Microsoft 365 controls.
• Limits to know: Power BI supports report-level comments but not native row-level writeback inside visuals.
  You still need a form or app to create comments and then read them into the model.
• Recommended patterns: Use SharePoint List + Power BI for simplicity or Dataverse + Power Apps + Power BI for stronger relational and record-level feedback.
  Consider built-in report comments for lightweight discussion or third-party visuals if you need embedded writeback.
• Practical steps to implement: Build the list (Teams or SharePoint), design a user form or Power Apps input, share it with internal users, then connect the list to Power BI and transform the data.
  Finally, add a feedback button or visual in your report to show related comments.
• When to add automation or Fabric: Choose Power Automate or Microsoft Fabric only when you need real-time sync, complex workflows, or large-scale processing.
  For simple capture-and-display without extra tooling, the list/table + form pattern avoids extra automation.

Video Summary and Context

Wyn Hopkins [MVP] published a practical YouTube walkthrough that demonstrates how to add commentary or feedback to Power BI solutions using Microsoft Lists and forms, while deliberately avoiding Power Automate. In the video, he takes viewers step by step from creating a feedback form to displaying responses inside a report, and he times each section so users can jump to parts they need. Consequently, the piece serves as both a tutorial and a design guide for teams that want a Microsoft-only workflow. Moreover, Wyn emphasizes real-world governance and user experience considerations throughout the demo.

How the Method Works

The central idea separates comment capture from reporting: collect feedback in a persistent store and then read it into Power BI for display. Specifically, Wyn shows using a SharePoint List or a Dataverse table as the comment store and a form or a lightweight app for input. Then, Power BI connects to that source and joins comments to the main data so readers can see recent feedback alongside metrics. As a result, you keep reporting clean while still making commentary available.

Step-by-Step Walkthrough from the Video

Wyn begins by creating a feedback list and then builds the list inside Microsoft Teams to make it easy for internal users to access. Next, he designs the form so that it captures metadata like author, timestamp, and related record keys, and he demonstrates sharing the form with colleagues. After that, he shows how responses appear in the list, how to connect the list to Power BI, and how to clean and transform the data for reporting. Finally, Wyn builds a simple feedback report visual and adds a button that opens the form, enabling readers to submit comments directly from the report experience.

Tradeoffs and Design Choices

Wyn outlines important tradeoffs when choosing between SharePoint List and Dataverse. The SharePoint List path is simple, familiar, and requires little setup, which makes it ideal for small teams or quick deployments; however, it lacks the more advanced relational features and governance controls you get with Dataverse. Conversely, Dataverse provides a stronger relational model, a built-in comments experience, and better integration with Power Apps, but it introduces licensing and governance considerations that may complicate adoption. Therefore, organizations must weigh ease of deployment against long-term manageability and compliance needs.

Challenges, Limits, and When to Use Alternatives

Wyn is candid about the limits of a no-automation approach: Power BI does not support native row-level writeback inside visuals, so you still need a separate input mechanism. This separation can create perceived friction because users jump from report to form, and feedback does not update in real time without refresh workflows. Additionally, security and permissions require careful setup so that list records do not expose sensitive data and so that report viewers can only see appropriate comments. For scenarios that need immediate sync or complex approval flows, Wyn recommends considering Power Automate or newer platform services like Fabric, even though they add complexity.

Practical Recommendations and Best Practices

To balance usability and governance, Wyn suggests keeping operational comments in a dedicated store, using a clear key to link comments to report rows, and offering a simple button or link from the report to the comment form. He also advises designing forms to capture context (for example the record ID and a short summary) so that analysts can filter and group comments easily inside Power BI. For larger deployments, consider the Dataverse option if you need record-level feedback with richer relations, but start with SharePoint List for pilot projects because it reduces barriers to adoption. Consequently, teams can iterate on UX and governance before investing in a platform with higher operational cost.

Final Takeaway

Wyn Hopkins’s video offers a clear, practical path for adding commentary to Power BI without building a custom backend or relying on immediate automation. His approach favors Microsoft-native tools and highlights the balance between simplicity and control, which many teams will appreciate. Finally, the tutorial guides viewers through a pragmatic implementation that works for many business needs while pointing out the moments when moving to Power Automate or a platform like Fabric becomes necessary. Overall, the video serves as a useful reference for teams that want to add writeback-style feedback with a controlled, familiar toolset.

Keywords

Power BI comments, Power BI feedback, Add comments to Power BI without Power Automate, Power BI lists and forms, Microsoft Lists Power BI integration, Power BI feedback forms, Power BI comment solution avoiding Power Automate, SharePoint Lists Power BI comments