What is changing
The roadmap describes the change in one sentence. When a user filters the report with a slicer or another supported report filtering experience, the Table edit visual should reflect that filter context. It should then show the relevant dimension records.
Table edit is the visual for editing dimension tables inside a Power BI report. Microsoft's documentation describes an interface for direct edits to dimensions in Power BI. Typical uses include creating new forecasting scenarios or versions. The Learn page also lists updating fixed values and changing the status of planning stages.
Two points follow from the roadmap text:
- It is a context change. The entry does not announce a new editing mode, new permissions or a change to where data is stored.
- The scope is narrow. The roadmap names the Table edit visual only. It is not a change to every Power BI visual or every Dynamics 365 Finance table.
My inference is that this should keep the visual in step with the rest of the page. Picture a planning report where a slicer narrows the view to one scenario or department. The editable dimension grid should narrow to match, not sit there showing everything. That is a convenience for planners, not a revolution. The roadmap does not say which filter types are supported beyond slicers.
What the visual already does
The Table edit visual already has several features. Don't credit any of them to this update. Microsoft's Learn page lists:
- Three editing modes: Grid, Row and Form. In Grid mode you can edit any record on a page and save from the visual. Row mode edits one record at a time and requires saving a new dimension value before adding another. Form mode shows records vertically with more attributes visible.
- Adding records with the plus sign in any mode.
- Batch update, which sets a value in a selected column for all rows shown.
- Grouping, fixed columns, date pickers, checkboxes for Boolean columns, number-type enforcement, and column filters and search.
- Admin controls for toolbar actions, hidden columns, locked or required columns, and URL, image and note columns.
One Learn detail matters for report authors. When you reference a column in these settings, admins configure functions through the visual properties button and the Visual UI section. The Learn page also says to use the column's technical name, such as msdyn_description, which you can find in the Data pane in Power BI.
Batch update deserves care once filtering is respected. Microsoft says it updates the selected column for all rows that are shown. If filter context changes which rows are shown, a batch edit will affect a different set of rows. Microsoft hasn't said how the two features interact, so test this before turning the feature loose on a production dimension.
Check report interactions first
Slicers in Power BI don't automatically reach every visual. Microsoft's slicer documentation says by default slicers filter all other visuals on the page, and you can change this with edit interactions. The procedure is:
- Select the slicer you want to configure.
- On the Format menu, choose Edit interactions.
- Filter controls appear above each visual on the page. Choose None on any visual the slicer should not filter.
Report authors should confirm the Table edit visual hasn't been set to None on pages where users expect filtering. The roadmap doesn't announce any special setup for this feature. This is ordinary Power BI configuration, and it explains why a slicer might not reach the visual even after the feature ships.
Slicers can also be synced across pages. Microsoft notes that if a slicer is synced to a page but not visible there, selections made on other pages can still filter that page's data. The roadmap doesn't say whether Table edit behaves identically in every synced-slicer setup, so test those cases.
Filtering is not authorization
Filtering what a user sees does not change what they may edit. Microsoft's Learn page says any user with the Update dimension data privilege can edit dimension values, and the out-of-box Administrator, Power user and Contributor roles include it.
Business performance planning also has dimension security. Admins grant access through dimension groups, with full access, read-only access or row-level access per dimension. Microsoft's security guide gives an example. If a user lacks edit rights to a specific scenario, they can filter their view to that scenario in Power BI or the Excel add-in. When they try to update amounts, a message tells them they lack permission. The guidance also lists Planning limited contributor and Planning viewer as unable to add, edit or remove dimension values through Table edit.
There is also a visibility rule. By default, only the user who creates a new dimension value can see it. Others can see it only if the dimension group grants all-values access or the value is explicitly shared. If a filtered Table edit shows fewer records than expected, check dimension group access before blaming the new feature.
Microsoft's security page also says Table edit is the exception to the rule that users need access to at least one dimension value per dimension in the cube. Don't generalize that exception to other visuals.
Rollout checklist for admins
Roadmap items can slip, so don't plan around a date. Use the time to prepare:
- Inventory reports that use Table edit alongside slicers or page and report filters.
- Audit visual interactions so slicers are set to filter the Table edit visual where intended.
- Test after the feature appears. In a non-production environment, apply representative filters. Confirm the records match expectations, then check that adding, editing, saving and batch update behave as before. This is my recommended validation, not a Microsoft-published procedure.
- Review permissions. Confirm roles and dimension groups match intent, and don't treat a slicer as an access control.
- Watch the roadmap. Microsoft removes items once they are generally available, cancelled or postponed.
Bottom line
This is a modest quality-of-life update to a niche part of the Dynamics 365 Finance planning toolkit. The documented gap is simple: a report page can be filtered while the dimension editing grid isn't. Closing it should make planning reports feel more coherent. The roadmap leaves the rollout day, the exact filter types and any performance effects unspecified. Treat the November 2026 date as an estimate, and verify the behavior in your own tenant before relying on it.