Skip to main content

Build an admin block UI extension

This guide is the second part of a five-part tutorial series that describes how to build UI extensions that display as actions and blocks in Shopify admin. Before starting this guide, you'll need to build or copy the admin action UI extension from the Build a UI extension for an admin action tutorial.

So far, you've created a UI extension for an action that enables buyers to create issues for a product. However, merchants need an easy way to see them. This guide demonstrates how to create a UI extension for a block in Shopify admin that displays buyer-created issues for a product.

The new block UI extension, at the bottom of the page. Two issues, created with the action, display.

In this tutorial, you'll learn how to do the following tasks:

  • Create a UI extension for a block that displays on the product details page.

  • Fetch information to populate the UI extension's initial state.

  • Connect the UI extension to Shopify admin's contextual save bar, when gathering input, for seamless page editing.

  • Run the UI extension locally and test it on a development store.

Requirements

Scaffold an app

Scaffold an app with the write_products access scope that uses Shopify CLI 3.78 or higher.

  • If you created a Remix app, then the write_products access scope is automatically granted to your app.
  • If you created an extension-only app, then you need to explicitly grant the write_products access scope to your custom app.
  • Add a product to your development store. The product should not have any custom variants at the start of this tutorial.

Project

Anchor to Create an admin block UI extensionCreate an admin block UI extension

Use Shopify CLI to generate starter code for your UI extension.

  1. Navigate to your app directory:

    Terminal

    cd <directory>
  2. Run the following command to create a new admin block UI extension:

    Terminal

    shopify app generate extension --template admin_block --name issue-tracker-block --flavor react

    The command creates a new extension template in your app's extensions directory with the following structure:

    Admin block structure

    extensions/issue-tracker-block
    ├── README.md
    ├── locales
    │ ├── en.default.json // The default locale for the extension
    │ └── fr.json // The French language translations for the extension
    ├── package.json
    ├── shopify.extension.toml // The config file for the extension
    └── src
    └── BlockExtension.jsx // The code that defines the block's UI and behavior

Anchor to Create an interface for the UI extensionCreate an interface for the UI extension

To create an interface for the UI extension, complete the following steps:

Anchor to Review the configurationReview the configuration

The UI extension's static configuration is stored in its .toml file. To display the issue tracker on product detail pages, set the target to admin.product-details.block.render.

To update the name that displays when merchants select the action from the menu, edit the name value in the locale files. To localize strings, a UI extension for an admin block uses the i18n API. This API gives you access to strings stored in locale files, and automatically chooses the correct string for the current user's locale.

Optionally translate your title to French.

Anchor to Use components to create the extension's UIUse components to create the extension's UI

Admin UI extensions are rendered using Remote UI, which is a fast and secure remote-rendering framework. Because Shopify renders the UI remotely, components used in the extensions must comply with a contract in the Shopify host. We provide these components through the admin UI extensions library.

You can view the source of your extension in the src/BlockExtension.jsx file. This file defines a functional React component that's exported to run at the extension's target. You can create the extension's body by importing and using components from the @shopify/ui-extensions-react/admin package.

Caution

The extension point in the component export must match the extension point that's defined in your .toml file, or the extension won't render.

To build your block's UX, return some components from src/BlockExtension.jsx. You'll create a simple UI to list out your product issues.

Anchor to Write the UI extension's logic and connect to the GraphQL Admin APIWrite the UI extension's logic and connect to the GraphQL Admin API

After defining the extension's UI, use standard React tooling to write the logic that controls it.

When you're writing UI extensions, you don't need proxy calls to the GraphQL Admin API through your app's backend. Instead, your UI extension can use direct API access to create requests directly using fetch. For merchants, this makes UI extensions more performant and responsive. This guide includes a utility file for GraphQL queries.

Your app can also get data from the extension APIs, which includes data on the current resource from the data API.

First, you'll need to populate the UI extension's interface with existing issue data. To do this, use direct API calls to query the metafield, and use the metafield data to populate a paginated list in the UI extension's block. Paginate issues to prevent the block from becoming too tall and difficult for users to use.

Create a new file at ./src/utils.js and add the GraphQL queries that the extension uses to read and write data to the GraphQL Admin API.

Import the getIssues utility method from the utils.js file. You'll use it to query the GraphQL Admin API for the initial data for the extension.

Anchor to Get initial data and set up paginationGet initial data and set up pagination

Use the getIssues utility method to fetch the initial data for the UI extension. Add a function to manage pagination.


Tip

At this point, you can use the Dev Console to run your app's server and preview your UI extension. As you preview the UI extension, changes to its code automatically cause it to reload.

Anchor to Update data and integrate with the page's contextual save barUpdate data and integrate with the page's contextual save bar

Next, you'll create a status dropdown and a delete button that enables users to either mark issues as completed or remove them entirely. When you create the status dropdown, you'll integrate it with the page's contextual save bar. This enables users to save changes to your block using the same controls that they would use to save changes to other fields in the Shopify admin.

Import the updateIssues utility method and use it to update the UI extension state.

Anchor to Handle status changes and deleting issuesHandle status changes and deleting issues

Add the functions to handle deleting and changing the status. Call the updateIssues utility method when the issue is deleted and when the form is submitted.


Tip

For more information on how to integrate with the contextual save bar, refer to this reference.

Anchor to Test the UI extensionTest the UI extension

After you've built the UI extension, test it with the following steps:

  1. Navigate to your app directory:

    Terminal

    cd <directory>
  2. To build and preview your app, either start or restart your server with the following command:

    Terminal

    shopify app dev
  3. Press p to open the Dev Console

  4. In the Dev Console page, click on the preview link for the issue tracker UI extension. The product details page opens. If you don't have a product in your store, then you need to create one.

  5. To find your block, scroll to the bottom of the page. It should display the issues that you've created so far.

The Dev Console, showing both UI extensions.
  1. When you change the status of an issue, the contextual save bar should display. The change is saved when you click the Save button.
The new block UI extension, at the bottom of the page. Issues that have been created with the action display.
Was this page helpful?