Power BI Desktop and Power Query in Excel follow the same principles that Power Query Online inside of Dataflow Gen2 does. We try to leverage lazy evaluation as much as possible, which means that we only compute things when they're absolutely necessary in an effort to prevent overloading your data source and/or your own resources in your desktop environment or the cloud.
This means that if you're working with a table that has billions of records and you perform some transformations that could be deemed expensive by your data source, that we will only request to compute around 200 rows of data for the data preview that we showcase, but the rest will not need to be computed and an exact number of rows that could be yielded by that specific step is not required in an effort to not overload the source.
You can, however, click on the "Transform" tab and click the option to "Count rows" which will give you the value that you're after inside of the Data preview
Recent ideas
Blocker: Purview must scan Fabric Warehouse tables/columns or we will deprecate Purview
Purview + Fabric Warehouse ≠ enterprise‑ready governance. In our environment, the Fabric Warehouse is the system of record, but Purview can only catalog the warehouse container—not the tables or co...Joshua_Hernande9 hours agoNew MemberNew180Views1like1CommentPower Query Parameter create/use when connecting to a dataflow
In power query when you connect to a table in a dataflow there are no options to create or use a parameter for that dataflow. When connecting to SQL there is an option when setting up the connection ...ben_holmes17 hours agoNew MemberNeed Clarification198Views3likes1CommentParameterize Dataflow Gen2 data source connection
Allow the Dataflow Gen2 data source connection GUID to be parameterized and stored in a Variable Library. This would allow the same Dataflow to use different connections depending on the workspace/e...frithjof_v17 hours agoCommunity ChampionNeeds Votes37Views2likes1Comment