---
title: "Adding Custom Widgets"
canonical: "https://help.cartinuum.com/space/WC/4538138693/Adding%20Custom%20Widgets"
format: markdown
---
Managed Experience Builder for ArcGIS supports custom Experience Builder widgets.

To make a custom widget available in Managed Experience Builder, you must first import an Experience Builder application that contains the widget.

Once imported, the custom widget becomes available for use in other applications within the same Managed Experience Builder environment.

### How Custom Widgets Work

Unlike [ArcGIS Experience Builder Developer Edition](https://developers.arcgis.com/experience-builder/), Managed Experience Builder does not install widgets directly.

Instead, custom widgets are discovered and registered when an Experience Builder application containing the widget is imported.

After the import is complete:

- The widget becomes available in the widget panel.
- New applications can use the widget.
- Existing applications can add the widget.
- The imported application itself does not need to be reused.

### Before You Begin

Ensure that:

- You have access to Managed Experience Builder for ArcGIS.
- You have an Experience Builder application that contains the custom widget.
- The application uses the same ArcGIS portal as your Managed Experience Builder environment.

#### Supported Versions

For best results, applications containing custom widgets should be created and published using the same version as running Managed Experience Builder.

[Refer to the Release Notes for the current version](https://help.cartinuum.com/space/WC/4514021429/Managed+Experience+Builder+for+ArcGIS).

Using different Experience Builder versions may result in compatibility issues or unsupported widget behaviour.

### Option 1 – Import an Existing Application

Use this option if:

- A colleague has provided an Experience Builder application.
- A vendor has supplied a sample application.
- The widget developer has provided a packaged application.

#### Step 1 – Obtain the Application ZIP

Obtain the published Experience Builder application ZIP file that contains the custom widget.

#### Step 2 – Start a Builder Session

Open Managed Experience Builder and start a builder session.

#### Step 3 – Import the Application

Import the application ZIP file into Managed Experience Builder using the **Import from my computer **option.

![image-20260619-041916.png](media://2e5b5b72-78f2-4d6c-8412-51b431d7d781)

#### Step 4 – Verify the Import

Once the import completes:

- The application appears in Experience Builder.
- The custom widget is registered within the environment.

The widget can now be used in new and existing applications.

### Option 2 – Create a Widget Container Application

Use this option if you have the custom widget source files but do not yet have an Experience Builder application containing the widget.

#### Step 1 – Open Experience Builder Developer Edition

Run ArcGIS Experience Builder Developer Edition locally.

#### Step 2 – Create a New Application

Create a new Experience Builder application.

The application can be minimal and does not need to be production-ready.

#### Step 3 – Add the Custom Widget

Add the custom widget to the application.

A simple page containing the widget is sufficient.

#### Step 4 – Publish the Application

Publish the application within Experience Builder Developer Edition.

#### Step 5 – Download the Application ZIP

Download the published application as a ZIP file.

#### Step 6 – Import into Managed Experience Builder

Import the ZIP file into Managed Experience Builder.

Once imported, the widget becomes available throughout the environment.

### Using the Custom Widget

After the import is successful:

1. Open Experience Builder.
2. Create a new application or edit an existing application.
3. Open the widget panel.
4. Locate the custom widget.
5. Add and configure the widget as required.

The original imported application does not need to be used unless desired.

### Updating a Custom Widget

When a widget is updated:

1. Update the widget in Experience Builder Developer Edition.
2. Publish the application again.
3. Download a new ZIP file.
4. Import the updated application into Managed Experience Builder.

The updated widget will then be available within the environment.

---

### Troubleshooting

#### The widget does not appear after import

Verify that:

- The application was created for the current version of Experience Builder.
- The application ZIP contains the custom widget.
- The application was imported successfully.
- The application uses the same ArcGIS portal as the Managed Experience Builder environment.

#### The widget appears but does not work

Verify that:

- The widget functions correctly in Experience Builder Developer Edition.
- Required services and data sources are available.
- The widget is compatible with the current version of Experience Builder.

### Best Practices

- Use matching Experience Builder versions whenever possible.
- Keep a copy of imported application ZIP files.
- Maintain a dedicated widget container application for each custom widget.
- Test widget updates before using them in production applications.