Updating a field value of another document when clicking over a boolean type in Sanity.io.

Hello Everyone! I have a question. How can i update a field value of another document when clic over a boolean type? I have the following schema:
The idea is that only one document can have the active field as true without the editor having to manually unchecked the previous selected event.

Hi User. This approach might get more complicated as you consider other parts of the picture, such as changes made outside of the studio (e.g., using the mutations API) that will not adhere to validation or document actions in the studio. If I might make a suggestion, I wonder if you might consider a different way of setting the active document, which is to have a singleton (e.g., a settings page) with a reference to a document. That document is the one considered “active” for this purpose, and when someone wants to change it they do so on that settings page (without worrying about conflicts, unsetting first, etc.). This would also permit changes to be made via the CLI or API.
If you want to stick with your current boolean approach, one method might be using validation (check if any other documents have the boolean set to true, and prevent publication if so). Another might be
document actions , where you could unset the field in the other document when you publish this one.

Hi ! Thanks for your response! This is my first time hearing about the singleton approach. Where can i find more information about it?

This is a good guide. Please let me know if you face any struggles and we’ll get your through them.

This is a good guide. Please let me know if you face any struggles and we’ll get your through them.

Great! Thank you!

This is a good guide. Please let me know if you face any struggles and we’ll get your through them.

I watched the video and it could work but i have question: If i create a 'Setting Page', does that mean that i will have to query the setting document instead of the event document?

Yes, you’d need to query it in some form. If your current query were:

Your new one might be something like:

Yes, you’d need to query it in some form. If your current query were:

Your new one might be something like:

That inner query would only return true in one instance—where the

_ref

property on the settings document’s

active

field is equivalent to the

_id

of the document being “considered” (as far as looping over documents goes).

Got it. I wasn't aware of the 'setting page' approach. That changes a lot of my schemas designs(luck me we are not in production with enough time to make those quick changes). THANK YOU User!!

You’re welcome! As I said, it’s not the only way to go, but I can anticipate problems with the boolean approach that are solved this way (and hopefully some time soon a release will make things even easier 😉).