Forum Discussion

PaisleyPrince's avatar
PaisleyPrince
Advocate II
2 months ago
Solved

Error in displaying data in a table

Hi,

I have a table with 251 records which i've loaded to a model and which includes one duplicate record. When i look at the table in the table view it correctly shows 251 records but when i put the table into a table visual i only see 250 and one of the duplicate records has disappeared. There are no visual, report or page level filters applied.

Would anyone be able to advise me why one of the duplicate records is not showing ?

Many thanks

Scott

  • Hi PaisleyPrince,

     

    This is expected if the duplicate record is identical across all the columns you placed in the table visual.

     

    The Data/Table view shows the physical rows in the model, so you see all 251 records.
    But a Power BI table visual shows the distinct combination of the fields used in the visual. So if two rows are identical across every displayed column, Power BI will show them as one row.

     

    To force both duplicate rows to appear, add a unique row identifier to the table, for example an Index column in Power Query:
    Power Query → Add Column → Index Column

     

    Then include that Index column in the table visual. If you do not want users to focus on it, you can move it to the end of the table or reduce the column width.
     
     

    🔍Parchitect
    Solutions Architect · Microsoft Fabric Specialist

    💡Helpful? Kudos are appreciated.
    ✔️Solved? Mark as Solution so others can find it faster.

  • Hi PaisleyPrince ,

     

    This is expected behaviour, not a bug. The Table visual in Power BI implicitly groups by the combination of all fields you drop into it, so two rows that are exactly identical across every column will collapse into a single row. The Data (Table) view shows the raw rows, which is why you see 251 there but 250 in the visual.

     

    What to try:

    • In Power Query, add an Index Column (Add Column → Index Column → From 1) to your table, then drag that index field into the Table visual. Each row becomes unique and both duplicates will show. You can hide the column by shrinking its width to zero.
    • If you don't want to touch the model, add any existing column that differs between the two "duplicate" rows (a key, timestamp, source row ID, etc.) into the visual.
    • Double-check there really is no filter in play — click the visual and open the Filters pane to confirm nothing is applied at visual/page/report level, and check the Selection pane in case a slicer is affecting it.

     

    A couple of quick questions:

    • Is the duplicate a true duplicate across every column, or only across the columns you've put in the visual?
    • Is this table standalone, or is it related to another table in the model? A many-side relationship can sometimes hide rows too.

     

    Useful links:

     

    Hope that clears it up.

    If this got you what you needed, a Kudos and an Accepted Solution mark would be great — it helps others searching for the same thing find the answer quicker.

4 Replies

  • v-abhinavmu's avatar
    v-abhinavmu
    Community Support

    Hi PaisleyPrince,

    Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to Dev_Dholakia & Parchitect  for sharing valuable insights.

     

    Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

     

    Thank you for being part of the Microsoft Fabric Community.

  • Hi PaisleyPrince,

     

    This is expected if the duplicate record is identical across all the columns you placed in the table visual.

     

    The Data/Table view shows the physical rows in the model, so you see all 251 records.
    But a Power BI table visual shows the distinct combination of the fields used in the visual. So if two rows are identical across every displayed column, Power BI will show them as one row.

     

    To force both duplicate rows to appear, add a unique row identifier to the table, for example an Index column in Power Query:
    Power Query → Add Column → Index Column

     

    Then include that Index column in the table visual. If you do not want users to focus on it, you can move it to the end of the table or reduce the column width.
     
     

    🔍Parchitect
    Solutions Architect · Microsoft Fabric Specialist

    💡Helpful? Kudos are appreciated.
    ✔️Solved? Mark as Solution so others can find it faster.

  • Hi PaisleyPrince ,

     

    This is expected behaviour, not a bug. The Table visual in Power BI implicitly groups by the combination of all fields you drop into it, so two rows that are exactly identical across every column will collapse into a single row. The Data (Table) view shows the raw rows, which is why you see 251 there but 250 in the visual.

     

    What to try:

    • In Power Query, add an Index Column (Add Column → Index Column → From 1) to your table, then drag that index field into the Table visual. Each row becomes unique and both duplicates will show. You can hide the column by shrinking its width to zero.
    • If you don't want to touch the model, add any existing column that differs between the two "duplicate" rows (a key, timestamp, source row ID, etc.) into the visual.
    • Double-check there really is no filter in play — click the visual and open the Filters pane to confirm nothing is applied at visual/page/report level, and check the Selection pane in case a slicer is affecting it.

     

    A couple of quick questions:

    • Is the duplicate a true duplicate across every column, or only across the columns you've put in the visual?
    • Is this table standalone, or is it related to another table in the model? A many-side relationship can sometimes hide rows too.

     

    Useful links:

     

    Hope that clears it up.

    If this got you what you needed, a Kudos and an Accepted Solution mark would be great — it helps others searching for the same thing find the answer quicker.

  • v-abhinavmu's avatar
    v-abhinavmu
    Community Support

    Hi PaisleyPrince,

    May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.


    Thank you.