Writeback Comments: How To Implement Them in Power BI & Power Apps

A Power BI report without an explanation only creates more questions, and the conversation moves to email, Slack, or PowerPoint until you find out why revenue missed plan. And by next month's close, that explanation is lost in an old thread or slide.  

The problem is that Power BI reports are read-only for viewers. The people who actually know the reason, like the regional manager, the plant controller, or the sales lead, can't add it to the report itself. To keep the explanation where the number is, use writeback comments. They let people write context straight into the report, next to the data, so it's still there month after month.

There are three ways to add writeback comments in Power BI: natively with Microsoft’s translytical task flows, with a Power Apps visual, or with Zebra BI Tables+ and Charts+ commenting in view mode.

In this article, we'll take a closer look at each method and explain the setup, the limits, and the best use case for each one.

What is writeback in Power BI?

Writeback in Power BI is the ability to change data directly from a report and send those changes to an application or database. By default, Power BI reports are read-only, so viewers can filter, drill down, or export, but they can't change the data or add anything to it.

There are 2 types of writeback:

• Data writeback lets users enter or change numbers, such as budgets, forecasts, targets, or corrections.
• Comment writeback lets users add explanations to the numbers, such as why a region missed plan or what's behind a spike in costs.

Power BI does have a built-in comments feature, but those comments sit in a pane next to the report, not on the data point they refer to. The number and its explanation end up in two different places, and readers have to look for the context.

Writing directly on the report isn't much easier. It requires editing rights, and most companies restrict those, since anyone with edit access can change or break the report.

However, you can fix both of these problems with writeback comments. They let people add explanations directly on the numbers, without edit rights and without changing the report itself.

Option 1: Native writeback with translytical task flows

You can write data back using translytical task flows, Microsoft's native way to do so from a Power BI report. You place a button or an input slicer in the report and connect it to a user data function, a short Python script that runs in Microsoft Fabric.

When a user clicks the button, the function writes their input to your data source, along with the report's filter context, so it's clear which product, region, or month the input belongs to. The feature has been generally available since the March 2026 Power BI update.

To make native writeback work in Power BI, you need:

• Fabric capacity. Translytical task flows run on Microsoft Fabric, so they aren't available without it.
• A Python user data function. Someone has to write and maintain the code that handles the writeback.
• A Fabric data store. The data is saved to a Fabric SQL database, a warehouse, or lakehouse files.

In DirectQuery and Direct Lake reports, changes appear immediately. In import mode, they appear after an automatic refresh.

Translytical task flow limitations:

Deployment pipelines: buttons don't rebind automatically when you move a report to another workspace, for example from development to production. They have to be reconnected by hand.

Embedded reports: translytical task flows only work in embedded reports that use secure embed.

For step-by-step setup, see Microsoft's translytical task flows tutorial.

When to work with translytical task flows

Translytical task flows are a good fit if your organization already runs on Fabric, you need to write back data such as budgets, forecasts, or corrections (not just comments), and you have someone who can write Python.

Option 2: Writeback comments with Power Apps

You can add comments with a Power Apps visual, an app built in Power Apps that runs inside your Power BI report. Users type their comment into a form in the app, and the app writes it to a data source like a SharePoint list or an Excel file.

The Power Apps visual passes the data from the report into the app, so each comment is saved with the product, region, or month the user had selected. The comments are then loaded back into the data model, so they can be shown next to the numbers.

Here's what you need to write back with Power Apps in Power BI:

• A Power Apps app. You build it in Power Apps Studio using Power Fx, a low-code formula language. The app is shared with users separately from the report.
• A data source for the comments. For example, a SharePoint list, Dataverse, a SQL database, or an Excel file.
• A comments table in the data model. The report loads the saved comments from the data source so they can be displayed.

New comments appear in the report at the next scheduled refresh. If the report uses DirectQuery and the app calls PowerBIIntegration.Refresh() after saving, they appear right away.

Power Apps writeback limitations:

• Records passed to the app: the Power Apps visual can pass a maximum of 1,000 records into the app.
• Browsers: the Power Apps visual doesn't work in Firefox.
• Report Server: it isn't supported in Power BI Report Server.
• Deployment pipelines: the app has to be re-shared in each environment, such as development, test, and production.

Power Apps writeback in practice

Despite its limitations, Power Apps can work well for teams that have the skills to build and maintain the app. Dutch telecom company KPN, for example, used Power Apps to build a writeback commentary system in Power BI. Their users can add and edit comments directly in their reports, and all comments are kept in one place, which makes them easier to track and manage. You can watch the KPN team explain their setup in the KPN customer story.

If you want to try this approach yourself, our webinar, Writeback Commentary in Power BI via Power Apps, walks you through the full setup.

Option 3: Writeback comments without Power Apps using Zebra BI Tables+ and Charts+

Both methods above need someone technical to build and maintain them, and and with Power Apps, new comments often don’t show up until the next refresh. If you just want the people who own the numbers to explain them in the report, there’s a simpler way: anyone who views the report can add comments, without Power Apps, code, or edit rights.

Zebra BI Tables+ and Charts+ are visuals that let Power BI report viewers comment directly on the numbers.

Viewers click a data point and type their explanation, and the visual saves it to an Excel file in your SharePoint, along with the filter context it was written under, such as the year, month, or region. The comment stays attached to that data point: change the filter and it disappears; change it back, and it’s there again.

Here’s what that means for your team:

• The explanation sits next to the number. The person who knows why revenue missed plan writes it directly on the data point, not in an email, a screenshot, or a slide. The next time someone opens the report, the number and the reason are in one place.
• Discussions stay in the report. Comments load without a dataset refresh, so a controller can ask about a number and the regional manager can answer in the same report.
• Everyone can add context. Viewers don’t need edit rights or Power BI skills to comment, so the people who own the numbers can explain them themselves.
• Decisions take less time. When the reason is already in the report, the monthly review doesn’t stop while someone chases it down by email.
• Your data stays in your tenant. Comments are saved to SharePoint in your own Microsoft 365 tenant, not to your dataset. They’re governed by your organization’s security and compliance policies, and Power BI and SharePoint permissions decide who can view and who can comment.

Here's what you need to set up Zebra BI Tables+ & Charts+:

Step 1: One-time IT setup

Your IT admin needs to complete a one-time setup, which takes about 30 minutes:

1. Turn on the AppSource Custom Visuals SSO setting in the Power BI admin portal.
2. Give one-time admin consent so the visual can read and write comments in SharePoint. It’s a delegated permission and can be revoked at any time.
3. If your organization blocks uncertified visuals, the admin first adds Zebra BI Tables+ and Charts+ as organizational visuals.

See the full IT setup instructions.

Step 2: Turn on viewer comments

Add Zebra BI Tables+ or Charts+ to your report. Drag the slicer fields you want comments to remember, such as year or month, into the visual’s Filters placeholder. In the visual’s comment settings, select Enable viewer comments and pick an Excel file in SharePoint.

Turn on the comment box and save the report. Anyone with access to the Excel file can start commenting. See the full setup guide for report editors.

Comments load directly from SharePoint, so you don’t have to wait for a dataset refresh. The visual loads the latest comments whenever someone opens the report page, changes a slicer or filter, switches report tabs, or refreshes the browser.

If a colleague adds a comment while you have the report open, you’ll see it the next time the visual reloads. Viewers can comment on any data point at any level of a hierarchy and highlight areas in a chart or table.

Several people can comment at the same time without overwriting each other, and one Excel file can hold comments from many reports.

Zebra BI Tables+ governance and security:

Your data stays with you. Comments are stored in an Excel file in your own SharePoint, and Zebra BI never receives or keeps a copy.

Full audit trail. Every comment and deletion is logged in the file with the user and a timestamp. Viewers don't see who wrote a comment by default, but admins can always check the file.

Zebra BI Tables+ limitations:

• Zebra BI Tables+ and Charts+ visuals only: comments in view mode can only be added in Tables+ and Charts+, though they also capture filter context from native Power BI slicers on the same page.
• Report Server: viewer comments don't work in Power BI Report Server because it doesn't support sign-in for visuals.
• Export and subscriptions: Tables+ and Charts+ aren't Microsoft-certified, by design, so they don't appear in static PDF or PowerPoint exports or in email subscriptions.

Tables+ is a good fit if you want business users, such as managers, controllers, or regional leads, to explain the numbers directly in the report, without code, edit rights, or waiting for a refresh. It's built for comments, not for writing back numbers, such as budgets or forecasts.

Can Power BI write back to Excel?

Yes, Power BI can write back to Excel, but not on its own. Power BI reports are read-only, so you need one of the three methods above to send input from the report to an Excel file. Each one handles Excel differently:

• Power Apps writes to Excel through the Excel Online (Business) connector. The file must be in OneDrive or SharePoint, formatted as a table.
• Native writeback doesn't write to a regular Excel workbook. It saves data to Fabric, in a SQL database, a warehouse, or lakehouse files.

Zebra BI Tables+ saves comments to an Excel file in your SharePoint automatically. It's built for comments, not numbers like budgets or forecasts.

Which writeback method should you choose?

The right method depends on what you want to write back, who should write it, and the setup you already have.

Translytical task flows work best if your organization runs on Fabric, you need to write back data like budgets or forecasts, and you have someone who can write Python.

Power Apps works well if you need custom forms or want to write numbers back to SharePoint lists or Excel, and you have someone comfortable with Power Fx.

Both are good options for writing back data or building something custom, but they take technical skills to set up and maintain. If you mainly want people to explain the numbers, Zebra BI Tables+ and Charts+ are the easiest place to start. Report editors turn on viewer comments in the visual’s settings, so there’s no code to write and no app to build or maintain. You don’t need Fabric capacity or a database either, because comments are stored in an Excel file in your own SharePoint. Viewers can comment without edit rights, and new comments don’t wait for a dataset refresh. Because Tables+ and Charts+ are built on Zebra BI Tables and Charts, you also get IBCS-compliant tables and charts and automatic variance calculations in the same visual.

Power BI Report Server isn’t supported by any of these methods. Native writeback requires Fabric, and neither Power Apps nor Zebra BI Tables+ and Charts+ work on Report Server.

Keep the explanation where the number is

A number without an explanation only starts a new email thread. Writeback comments keep the answer in the Power BI report, next to the data, so it's still there at the next close.

The truth is that all three methods can get you there. Translytical task flows suit Fabric teams that need data writeback and can write Python. Power Apps works for custom forms and writing numbers back to SharePoint or Excel. And if you want the people who own the numbers to explain them directly in the report, without code, edit rights, or waiting for a refresh, Zebra BI Tables+ is the quickest way to start.

Pick one report your team reviews every month, turn on viewer comments, and let the people who know the reasons write them down at your next close. Try viewer comments in Tables+ with Zebra BI's 14-day free trial.

Frequently Asked Questions