microsoft / microsoft/AzureStorageExplorer

Cannot display a table if there is a property named lowercase-p "partitionKey"

Open
#8,574 6 comments 0 reactions 1 assignee View on GitHub

@craxal is already working on this.

Since May 19, 2025.

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

Description

Storage Explorer Version

1.38.0

Regression From

No response

Architecture

x64

Storage Explorer Build Number

No response

Platform

Windows

OS Version

Windows 11

Bug Description

I've found that if I have a property in my entity called partitionKey with a lowercase "p", this is allowed by Azure Tables, but Storage Explorer will display a blank tab.

Image

This is not a big deal, I was able to remove the offending data. However, sometime between 1.24.3 and now the UI changed. In 1.24.3, you'd get a blank page of results and a spinner that ran indefinitely. You could then enter a query and as long as it didn't cross the bad entity you'd get results.

However, in 1.38.0 and a couple other versions I tried you end up with just the blank screen in the screenshot above and the whole table is basically inaccessible.

I know the first thing you're going to say is "Why would you create a property called partitionKey when you know that there's already PartitionKey and that's important?" It had to do with creating an entity that defined a job that was scanning other entities. So there was a parameter called tableName and and called partitionKey to define the entities the job would be acting on.

Anyway, once I deleted that property from the entity the table started working again.

I also discovered the following:

  • rowKey with a lowercase-r also fails in the same way.
  • timestamp with a lowercase-t allows you to see the search results, but the bad value shows up in the regular Timestamp column
Steps to Reproduce
  • Navigate to the table in a tool OTHER than Azure Storage Explorer (I used the Storage Browser in the Azure Portal)
  • Create a test table.
  • Add an entity. PartitionKey and RowKey can be anything. Also add a property called "partitionKey" with a lower-case p, with any value.
  • Try to open the table in Azure Storage Explorer.
  • It will just display as blank and you will not be able to access the table at all.
Actual Experience

You cannot open the table. It shows as a blank tab.
Image

Expected Experience

Ideally, you'd be able to see the entity. Naming a property "partitionKey" is surely not best practice, but it is allowed by Tables.

Failing that, an error message should display, or be logged in the Storage Explorer logs, or in the system Event Viewer, that would allow a user to troubleshoot why their table doesn't work.

Or at the very least, display the table without the offending entity so that other entities are still available to the user.

Additional Context

No response

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.