Forum Discussion
Table visual object not displaying data on columns
Hi DannyVos93 ,
Thanks for the update.
you are using OData and the data is fine in the query but disappears in the table visual, it seems like a rendering issue due to too many columns.
To fix this, try splitting the table into two visuals with fewer columns each or create a new table visual and add columns one by one to see which one causes the issue. Also, check if the column data types are set correctly in the model view. You can use the Performance Analyzer in the View tab to check if the visual is slowing down.
if you are still facing issue , we will help you to resolve it
If this helps, please accept as a solution and give a kudos so that other members can easily find it .Regards,
HarshithaHi there, I'm sorry I couldn't get back to you guys earlier.
We finally solved it. What we did was that we rebuilt the whole table visual and we realized that for the fields we were entering on the table, we were sometimes aggregating them (showing as sum, or average) and other times we would put them as dont't summary. After we left all the fileds as Don't summarize, and as Show items with no data, the information would all be displayed as expected and no missing data points were identified.
Thank you for the help troubleshooting this!
Hi DannyVos93 ,
Yeah, I've run into this kind of thing before in Power BI, especially with table visuals that have a lot of columns or calculated fields. A couple of things you might want to check:
- Sometimes if you have too many columns, especially with complex calculated columns or measures, Power BI visuals can start acting weird, and some columns might not show up as expected. It’s not always about the number of columns, but more about how heavy the calculations are or if there are any columns producing errors or blanks behind the scenes.
- Try checking if any of your calculated columns/measures are returning blanks or errors for certain rows, even if it looks fine in the query. Sometimes DAX can behave differently in the visual vs. the data view.
- Also, if you’re using DirectQuery, visuals might struggle if the query gets too complex or if column types are mismatched.
- Field order usually shouldn’t matter, but sometimes rearranging them does fix odd glitches, as you’ve noticed. You could also try creating a brand new table visual and add the columns back in slowly to see if there’s a specific column or combination that triggers the issue.
- Lastly, make sure you’re on the latest version of Power BI Desktop—visual bugs do get patched pretty often.
Hope this helps a bit! Would be interested to hear if you find the culprit or if you have a sample file you can share, sometimes that makes it easier to troubleshoot. Good luck!
translation and formatting supported by AI