microsoft / microsoft/AzureStorageExplorer

Import CSV into table: Offer option to not import empty CSV rows

Open
#3,136 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:bulb: setting candidate :gear: tables
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Is your feature request related to a problem? Please describe.
I just took a CSV export from Azure DevOps and was deleting several rows from it in Excel. I didn't realize, as I deleted rows, Excel was replacing deleted rows with lines of empty commas in the CSV file itself (e.g., ,,,,).

So, when I uploaded my 10 rows, it still processed 1,247 additional empty rows. These empty rows didn't result in a bunch of new table rows, though the import messaging implied they would as it handled, saying "1247 entities imported". Instead, I believe each empty row was repeatedly merged into a single empty row created by the first empty row encountered.

Describe the solution you'd like
I'd love an import option where I can ignore any rows in a CSV file that consist entirely of commas.

Describe alternatives you've considered
I ended up opening the CSV file in VS Code to delete empty rows before I did my next import.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not mention specific files, tests, or entry points. Start by locating the Azure Storage Explorer table CSV import flow and its import-row counting behavior. Done means an import option can skip rows consisting entirely of commas and the reported imported count matches the rows actually processed.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.