Data inventory

Every name your data is stored under, read straight from the database: the record types, the fields on them, the settings, and our own tables — each with a count beside it. Nothing here changes anything. It exists so a question about your data can be answered by looking rather than guessing.

Most people will never need it. It is here for two moments: when support asks what an install actually contains, and before anything that moves data around, so there is a picture of what was there beforehand to check against afterwards.

Example

Something looks wrong with a field on your dogs. Rather than guess, you open Data inventory, see that the field is present on 214 records, and send the JSON to support — who can now see the shape of your data without asking you to describe it.

FAQ

Is it safe to open on a busy site?
Yes. Every question it asks is a count, and it never writes. It caps each list so a very large site cannot hang the page.

What does “no namespace” mean?
Some of our field names are plain words — breed, address — rather than something obviously ours. They are safe where they are, because they sit on our own records. It is flagged because anything that renames fields by matching our prefix would skip them, and a missed field does not announce itself: it simply comes back empty.

Why does the copy button give me JSON?
So the whole picture travels in one piece. Paste it into a question on the support site and nothing is lost in retyping.

Can I change anything from here?
No. There is no form on this screen and nothing to submit. If something needs changing, it is changed where it lives.