> For the complete documentation index, see [llms.txt](https://docs.gridmate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridmate.io/package-reference/components-library/utilities-and-monitoring/gm-data-import-monitor.md).

# GM - Data Import Monitor

(gmpkg:dataImportMonitorLWC)

## **Documentation**

**GM - Data Import Monitor** component is a utility bar item that lists the data imports started by the current user from a grid import wizard. Each import is processed through Bulk API jobs; the monitor shows the file, the object, the operation (Insert, Update, Upsert) and the progress. When a job is complete, the user can download the results and, if any record failed, the errors as CSV files. An import can be removed from the list at any time.

{% hint style="info" %}
The import list is stored in the browser local storage. It is specific to the user and to the browser.
{% endhint %}

**Use case:** Add the monitor to the utility bar of a Lightning app to follow the progress of data imports and get the error file. See [Grid Data Import Wizard](https://docs.gridmate.io/advanced-guides/filters-and-data/grid-data-import-wizard.md).

## **Specification**

This component has no properties.

## **API Reference**

{% tabs fullWidth="true" %}
{% tab title="dataImportMonitorLWC.js-meta.xml" %}

```xml
<?xml version="1.0" encoding="UTF-8" ?>
<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
    <apiVersion>65.0</apiVersion>
    <isExposed>true</isExposed>
    <masterLabel>GM - Data Import Monitor</masterLabel>
    <description>Data Import Monitor</description>
    <targets>
        <target>lightning__UtilityBar</target>
    </targets>
</LightningComponentBundle>
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gridmate.io/package-reference/components-library/utilities-and-monitoring/gm-data-import-monitor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
