Forum Discussion
Resolver IQuery editor shows rows but data is not available in data view
Dear all,
one of the issues we found is that in a certain table an array was present and CDS did not handle this the way it was expected. Instead of using CDS we now use ODATA (and manipulated the applicable table), which allows us to link to the necessary data/tables. Using ODATA, in our case, also solves some other random issues like Timeouts.
Community SupportHi Richard77 ,
I can't reproduce your issue.
Could you check if all rows show in Power BI Desktop Data View, not Report View?
In addition, please check if any other slicers, filters or visual interactions affect the result.
Best Regards,
Icey
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Resolver IDear Icey,
there is no 'header' table nor a 'parent-child' relationship. So far, together with a developer, we have confirmed that the data in D365 is correct and has a unique column.
Adding an index column does not work (404 rows become 360), 'Group by' does not work (it leaves 404 unique rows).
I have found one solution that works, but i'm not very confident that this should be it, and that is when i merge the table 'WorkerEntity' with the applicable 'WorkerHolidayBalanceEntity' based on the column personnel number. Adding simply the name of an employee in 'WorkerHolidayBalanceEntity' via this merge i get all the applicable rows (404) in the report view.
So we now have a workaround but no solution for the issue.
Cheers,
Richard