microsoft / microsoft/vscode-documentdb
Export Data to CSV and Excel 🚀
@BChoudhury-ms is already working on this.
Since Jul 28, 2026.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 22
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 21
Description
Export Data to CSV and Excel: Feedback and Collaboration Welcome! 🚀
We propose a feature that enables exporting data to CSV and Excel files directly within the DocumentDB for VS Code extension. Here’s what we envision and how you can contribute to shaping this capability.
Proposed Feature Overview
Export your data to CSV or Excel with flexible and user-friendly options. This feature is designed to enhance data workflows, catering to diverse user needs—whether managing complex NoSQL documents or traditional relational data.
Core Features
-
Export from Multiple Contexts
- Export data from the tree view or query editor/collection view.
- Tailor exports to suit your workflow, whether for specific resources or detailed query results.
-
Full vs. Filtered Data Export
- Export entire datasets or specific query results.
- Filter and refine exported data to match exact requirements.
-
Customizable File Output
- Define file names, paths, and save locations to align with your organization system.
-
Data Preview Before Export
- Preview your data to validate its accuracy before exporting.
- Adjust configurations easily for precise results.
-
Field Selection
- Choose which fields to include for full customization of the export.
- Reduce noise by excluding unnecessary attributes.
-
Advanced Data Handling
- Embedded Objects: Export as nested structures or flatten for simplicity.
- Arrays: Expand into rows/columns or keep compact for analysis.
- Custom Formatting: Apply rules for date, numeric, and text fields.
-
On-the-Fly Filtering
- Add filters directly during export to refine results without modifying original queries.
We Need Your Feedback!
Discussion Areas
We aim to build this collaboratively, starting with the ideas outlined above. Your input can make this feature more robust and aligned with community needs.
Here are some specific ways you can contribute:
- Do you see additional use cases we haven’t covered?
- Are there specific challenges you face when exporting data that we should address?
- What’s your preferred handling for complex structures like arrays and nested objects?
Join the Conversation
Leave comments, suggestions, or additional feature requests directly in this issue. Every suggestion is valuable and will help shape the final implementation.
How It Will Work
-
Schema Discovery
- A unified abstraction layer (
SchemaScanner) will normalize schemas across SQL and NoSQL databases, simplifying export workflows.
- A unified abstraction layer (
-
Preview and Configuration
- Users will preview data and toggle fields to customize outputs.
- Flexible settings ensure usability across different database structures.
-
Export Process
- Data will be generated into CSV or Excel formats based on user configurations.
- Options for advanced filters, formatting, and output destinations will be included.
Draft Development Plan
-
Requirements Finalization
- Confirm supported databases, workflows, and key scenarios.
-
Schema Abstraction
- Implement
SchemaScannerto unify relational and NoSQL schemas. - Build adapters for DocumentDB, MongoDB databases, SQL, and other databases.
- Implement
-
Preview and Field Configuration
- Develop an interactive UI with React and SlickGrid.
- Enable users to configure exports dynamically.
-
Data Export Logic
- Build functionality for CSV/Excel generation.
- Address nested and hierarchical data structures.
-
User Experience Enhancements
- Add tooltips, validation, and performance optimization for smooth usage.
What’s Next?
This is just the starting point. We anticipate multiple iterations based on your feedback. Each iteration will refine functionality, ensuring it meets community needs and delivers a reliable user experience.
We look forward to hearing your thoughts! Let’s work together to create a flexible export feature for the DocumentDB for VS Code extension. 🌟
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.