[Feature Request]: Edit Data new entry point flow

[yoleichen]

Feature Description

• I can right-click on a table and hover over Edit Data to open a submenu with two options: Top 100 rows, Custom.

• I can choose Top 100 rows, which opens the Edit Data tab and automatically loads 100 rows.
• I can choose Custom, which opens an editable dropdown where I can specify how many rows to fetch.
  • I can see ghost text in the dropdown that says: “Set total rows to fetch.”
  • I can type any number into the dropdown or select from preset values: 10, 50, 500, 1000.
  • I can press Enter to confirm my input and it loads the number of rows I specified.

See more design details from Figma design mock

Problem and Motivation

Users need a clearer, more deliberate way to specify how many rows to load before entering the Edit Data experience. Introducing row selection directly from the table context menu makes this decision explicit, discoverable, and harder to accidentally dismiss this setting. This approach better supports both quick inspections and more intentional data editing scenarios.

Related Area

• Connection dialog (SQL Server | Azure browse/Fabric browse)
• Query editor
• Query results panel
• Object Explorer
• GitHub Copilot integration
• Preview/Edit data
• Table Designer
• Schema Designer
• Schema Compare
• Local SQL Server Container provisioning
• SQL database in Fabric provisioning
• DACPAC/BACPAC export/import
• SQL Database projects
• Query Plan Visualizer
• Other (please describe below)

If you selected "Other", please describe the area

No response

Confirmation

• I have searched existing feature requests and couldn't find a match
• I want to help implement this feature

[kburtram]

Is setting a custom number of rows to edit common enough to warrant a new submenu and separate command? This would add some complexity to the entry point for a use case that may not be very common. In most scenarios, is editing the default 100 rows sufficient?