On a report that connets via Direct Query to a MS SQL Server database table, a data table with 11,454 rows (9.71 MB) in it exports to a .csv with 11,454 rows. Without modifying anyting, the file was published to a workspace on a premium embedded node. When navigating to the report on the PowerBI online service, one exports from the same table visual. The resultant .csv has only 10,490 rows (8.89 MB).
Searching on the report utilizing the primary key for some of the records that fell out utilizing a page level filter, they suddenly appear on the table visual like normal, and the records are able to be exported. However, they are not being included in the data export when the page level filter is not in place.
11/21/2018 Edit: This is directly affecting a client utilizing our embedded reports. This is a severe breach of trust between us and the client when there are nearly 1,000 rows disappearing without warning or message, when this was approved using the desktop exports. Please advise when we can speak with a Microsoft PBI representative regarding this.
v-xiaoyan-msft
on:
Report jumps between two profile logins.
on:
Get External Data: Power BI semantic models throws...
Idrissshatila
on:
Timeline slicer is showing 30 & 31 March under 30 ...