Sitecore GraphQL Mutations: A Complete Guide

 

Introduction

While queries handle data retrieval in GraphQL, mutations are responsible for creating, updating, and deleting content in Sitecore. Let's explore how to effectively use Mutations in Sitecore.

1. Create Mutation:

mutation CreateItem {

  createItem(

    name: "New Item to be Created"

    template: "{4330C04F-5CAA-4E93-A2B2-634900395E51}"

    parent: "{C081F940-3F38-4E10-8F43-B80AA63BC1BA}"

    language: "en"

    fields: [

      { name: "title", value: "'New Item Created with Mutations'" }

      {

        name: "subtitle"

        value: "'This is Sitecore New Item Created with Mutations'"

      }

    ]

  ) {

    path

    id

  }

}

In this example:

  • createItem is a mutation function that creates a new item.
  • name is the name of the new item.
  • parentId is the ID of the parent item under which this new item will be created (you can get the parentId of an existing item in the Sitecore content tree).
  • templateId is the template ID for the new item, which defines the fields and layout of the item.

2. Update item

mutation UpdateItem {

  updateItem(

    path: "/sitecore/content/Home/MyProject/MutationsItem/Cretaed MutationsItem"

    language: "en"

    version: 1

    fields: [

 { name: "title", value: "'Item updated'" }

 { name: "subtitle", value: "'This is Sitecore Item updated with Mutations UpdateItem'" }

 ]

  ) { 

 id 

 name 

 fields { 

 name 

 value 

  } 

  }

  }


In this mutation:

  • path is the path of the item you want to update. we can pass itemid as well instead of path.
  • fields is an array of field names and their new values.
  • The response includes the updated item’s id, name, and the updated field values.

13. Delete item

mutation DeleteItem {

  deleteItem(

    path: "/sitecore/content/Home/MyProject/MutationsItem/Item updated"

  ) 

{ success }

}

In this mutation:

  • path is the path of the item you want to delete, we can pass itemid as well instead of path
  • The response includes a success flag to indicate whether the deletion was successful.

Comments

Post a Comment

Popular posts from this blog

Setting Up Sitecore Headless with Next.js in Disconnected Mode

Image
Sitecore Headless CMS offers a flexible way to integrate with different frontend technologies. For developers working with frameworks like Next.js, Sitecore provides various ways to set up the environment, including four distinct modes: Disconnected Mode , Connected Mode , Integrated Mode , and API Mode . Each mode offers unique features for different stages of development and production needs. What Is Disconnected Mode? Disconnected Mode is designed for local development and testing without requiring a direct connection to the Sitecore platform. In this mode, data is typically retrieved from static files (like YAML or JSON), and content updates are done manually. This mode is ideal for frontend developers who want to focus on building the user interface and the site’s functionality without waiting for backend integration. In Disconnected Mode , the data flow is not dependent on the Sitecore CMS. Instead, content is stored locally in static files, which are easier to manage and qu...
Read more

Translating Sitecore items’ field values into different language with PowerShell and Translate API

Image
Recently, we encountered a situation where we needed to translate multiple Sitecore field values across numerous items into different languages. Manually handling each item and field was both time-consuming and complex—especially since actual translation was required, not just copying values between language versions. We explored various approaches to streamline the process. While AI-based solutions seemed promising, but client side Compliances for AI usage ruled out that option. Another practical alternative was to use spreadsheets like Excel or CSV files containing translated content and then import those values into Sitecore using PowerShell scripts. During our exploration, we discovered a freely accessible translation API that doesn't require an API key. By leveraging this in our PowerShell script, we were able to automate the translation process and directly apply the translated content to the appropriate language versions of the Sitecore items—saving both time and effort. ...
Read more

Create Sitecore Ribbon Button using Sitecore PowerShell Extensions

Image
Creating a custom Ribbon button in Sitecore using Sitecore PowerShell Extensions (SPE) involves several steps, which I'll guide you through below. The general process includes Create PowerShell Script Module and Add Integration Point Setup the PowerShell script Library and Add PowerShell script Configuring the Ribbon button and Sync Verify the button in the Ribbon Here's how we can achieve that: Pre-Requisites: Running Sitecore Instance PowerShell ISE to run PowerShell script (Install compatible Sitecore.PowerShell.Extensions if it’s not there) Step-1: Create PowerShell Script Module and Add Integration Point Create PowerShell Script Module: Go to Content Editor . In the content tree, navigate to: System > Modules > PowerShell > Script Library . Right-click on Script Library and select Insert > PowerShell Script Module . Give it a name, su...
Read more