Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
9 months ago
Solved

Create a Dynamic Column in a Table Visual

I am trying to create a table visual with a dynamic column that lets the user change the value in that column for each row. For example, the table columns are vendor, settle amount, days to pay, prop...
Need Help
  • Amar_Kumar's avatar
    Amar_Kumar
    9 months ago

    Anonymous 

    No, this is not possible in Power BI table visuals.

    Power BI visuals are read-only. Users cannot directly edit values per row in a table and have measures recalculate in real time.

    Why this doesn’t work in Power BI:

    1. Table visuals do not support per-row user input.

    2. Slicers apply the same value to all rows in the current filter context.

    3. Measures recalculate only from model data or slicer/filter context, not manual edits.

    4. Power BI has no concept of “write-back” or editable cells.

    What is possible (workarounds):

    Option 1: Disconnected parameter table (limited)

    • You can let users select a value via slicer or parameter

    • But it applies globally or by filter, not per row

    Option 2: “What-if” parameters per scenario

    • Create multiple scenario columns (Scenario A, B, C)

    • User switches scenarios, not individual rows

    Option 3: Use Power Apps (best workaround)

    • Embed a Power Apps visual

    • Allow users to edit Proposed Days to Pay per vendor

    • Write values back to a data source (SharePoint, Dataverse, SQL)

    • Refresh or DirectQuery updates PNL measure

d_m_LNK's avatar
d_m_LNK
Icon for Super User rankSuper User
9 months ago

To do that in each row isn't possible with the table visual.  What you describes sounds like maybe the need for more slicers or a field parameter to filter the table in different ways to get the results they want.  If they are looking for a table of rows that each have different filters, I'm not sure how you would do that just because of how Power BI works.

 

You may be able to create a calculated column based on the vendor specific logic they are seemingly needing.  That way your measure would be able to do the vendor specific calc instead of changing the cells on the table.