Error when trying to open a specific post in Sanity Studio, resolved with command line editing.

Hi! I’ve just started trying to learn sanity and I’ve been working on an image blogging project. Everything was working well to the point I was at until I tried to implement a “saving” feature in my code I called an object when I should have called an array and seem to have broken something in the post I was trying to save. Now, when I try and view the post in the sanity desktop i can see the item but cannot edit it or see it’s details I keep getting the following error:












I have to reset the Desk tool to get back to a content view. I can add new items and edit/delete them in the Desk tool, but I can’t do anything with the one that I tried to save using the wrong code. Is there any way to delete this item or reset the contents of this schema without resetting the whole dataset? Or a way to fix this error?

Hi . To confirm, are you getting this error in your Studio when you try to open a particular document?

I believe the answer is yes. Forgive me I’m not completely comfortable with sanity terminology references yet. Speaking in purely db terms I would refer to it as a “record”. In table vernacular I would refer to it as a row.
In my dataset I have four schemas. One of them is to hold the actual posts being made. I can see my dataset in the Desk tool. I can see Contents and my four schemas. I can click on the posts schema and see all of the posts made. Clicking on this one particular post crashes the tool with the error I posted. I can’t get into the post to delete it with the tool features. Every other post is fine because I never tried to use the faulty Save action on them.

Thanks for confirming. In that case, if you’re comfortable using the command line, you can open the JSON directly in your editor and make the necessary edits.
1. When you open the post in the Studio, its

_id

will be part of the URL in the browser’s location bar. It might look something like , in which case you will want to copy

14f09fac-ddad-d4d4-9ed5-4b12346b3f90

.2. In your terminal, navigate to your Studio directory. Once there, enter the command
(replacing with your

_id

). This will open the document as JSON in your terminal’s default editor. If it’s not using an editor you’re comfortable with, try preceding the command with `VISUAL=<yourEditor>`; for example, if you use VS Code the above would be .3. Edit the JSON to remove the problem. If you’re not sure, feel free to post the entire file here. If it’s sensitive, you can DM me the JSON and I’ll take a look.
4. Save the file and close your editor. You should get a message that the document was upserted; if the process keeps running in your terminal, you can safely kill it with Ctrl-C.
5. Open the document in the Studio to confirm it’s working.

Hey Geoff,
Once again forgive me for the extended delay in this response. I do appreciate the help you’re trying to offer.

Ultimately I was able to use your advice to fix the problem, but there was a bit of a wrinkle. Using the _id that showed in the Desk tool URL was not affecting anything that was being displayed. After a lot of poking around and trying things I probably shouldn’t have, I finally noticed that on the actual displayed site I am building when you clicked on the post to see details which wasn’t functioning because of the error the _id that showed in that URL also started with the word “draft”. Even though the post had been published, it somehow got stuck in a draft stage when I tried to originally save it with the bad code. Editing that _id variant solved the issue and I was able to get into the post in the Desk tool and delete it.

Thank you for your help.

Great! Glad to hear you got this resolved! 🙌