When working with large datasets via Direct Connect, eg via Azure SQLDB, the default choice when selecting a field in the well is not always appropriate. For example you might want to count a high cardinality text field. In the current preview, as you select the field, it tries to go get all the individual values (potentially millions) to display. The idea is to have a "delayed calculate/query" selection mechanism where you can prepare fields and filters and then hit go.
1 Comment
- fbcideas_migusrNew MemberStatus added:Needs Votes
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