# Mapping attributes

> By mapping attributes, you are filling up **AppOne** with data used for analyses. If certain attributes that are important for dashboards are not available, the dashboards are not shown in **AppOne**. For example, by mapping the attribute **User**, the **User** menu becomes available in **AppOne**.

## Introduction

By mapping attributes, you are filling up **AppOne** with data used for analyses. If certain attributes that are important for dashboards are not available, the dashboards are not shown in **AppOne**. For example, by mapping the attribute **User**, the **User** menu becomes available in **AppOne**.

On the other hand, since attributes for which no values are available are not displayed in **AppOne** these attributes do not need to be mapped.

If your input data set contains exactly the same attribute names as the attributes defined in the **Basic Connector**, the attributes will automatically be attached to the proper attributes in the **Basic Connector** when loading your data.

## New attributes

It is possible that there are attributes in your input data file that do not correspond with the attributes in the **Basic Connector**. In this case the attributes are not matched automatically. These attributes will be detected when uploading your data. See the illustration below.

![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-53780-7240b54f-1a89cb52.webp)

In this case, you must map the attributes in your data file to the proper attributes in the **Basic Connector**. If there are no corresponding attributes available in the **Basic Connector**, the new attributes must be added to the **Basic Connector** first.

Follow these steps to map new attributes to the corresponding attributes in the **BasicConnector**.

| Step | Action |
| --- | --- |
| 1 | Double click on the attribute that needs to mapped in the `Cases_events_input` table.  The **Edit Datasource Attribute** dialog is displayed, containing properties of the attribute. See illustration below. |
| 2 | Click on the value in the field next to **Name in data source**. |
| 3 | Select the proper attribute and click on **OK**. |

![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-54344-114b6474-98149c1f.webp)

## Input format settings

If the data attribute in your input data has a different format than the corresponding attribute in the **Basic Connector,**, for example, a different date format for the **Event end** attribute, an error is displayed in the **Values list** of the **Edit Datasource Attribute** dialog.

See the illustration below.

![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-54820-1a8227e3-28abdc16.webp)

To solve this, select the right format in the Date format and/or Time format or use the **AUTODETECT** button.

## Event order

Events are ordered based on its `Event_start` and `Event_end`. However, some activities may start and end at the same time. To ensure the correct order, you can define the `Activity_order` expression attribute. If you do not define the activity order in the connector, the activities will be ordered alphabetically.

See the comment in the illustration below for an example expression to define the activity order.

![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-54300-7d79f8b3-9a6a1000.webp)

## Default period filter

The `Global_settings` table in the **Basic Connector** contains a `Default period` expression attribute to determine the default setting of the period filter within **AppOne**. This is the default time range presented to the end users in **AppOne**. The `Global_settings` table will be outputted as part of your dataset and used within **AppOne**.

Follow these steps to change the default setting for the period filter in **AppOne**.

| Step | Action |
| --- | --- |
| 1 | Right-click on the **Default period** expression and select **Edit…** to open the **Edit Expression Attribute** dialog |
| 2 | Change the expression to the default you want to use in **AppOne**. Some examples are available in the comments of the **Edit Expression Attribute** dialog. See illustration below |

![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-57549-53e077f5-1d6f4aae.webp)

## Checking the data in the Basic Connector

Before you create and export the output data set it is advised that you check if the data from the input data file is properly connected in the **Basic Connector**.

The **Output** menu in the **Basic Connector** contains tabs to check the data for all defined tables. In this example, we check the `Cases base` and the `Events base` charts.

The numbers on the top right also show you how many cases there are in the input and output.

:::note
If you have cleaned the data, the difference between output and input indicates how much cases are filtered out.
:::

It is a good check to see if the number of cases matches with the number of cases in the input files that are loaded into the **Basic Connector.**

![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-53880-a5e887b3-7f400a69.webp)

In the **Basic Connector** you can also create a dashboard item, for example a Process graph, to check if the data is properly connected.

## Data grid

Next to the debug charts, it can be helpful to view the data in its table structure. In **UiPath Process Mining** this can be done in the data grid in the **Tools** panel.

The data grid can be accessed by expanding the **Tools** panel in the left bottom corner and can be used to display attributes of a table in the **Basic Connector**.

The data grid only works if a chart is selected that is based on the table. Attributes can be displayed by drag and drop or by right-clicking the data grid.

![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-54052-e2b4205e-3e614ed9.webp)

:::note
**1.** The data grid can be sorted by clicking on the headers of each column. **2.** Every filter applied to the selected chart is also applied to the data grid.
:::