> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/textual-integrations/microsoft-fabric-integration/fabric-entity-types.md).

# Identifying and configuring replacement of entity types

## Syncing files to detect entity values <a href="#sync-files" id="sync-files"></a>

Next, you run a scan on the files to identify values for Textual entity types. To start the scan, click **Sync files**.

<figure><img src="/files/leAW1Dw13EL7YHUHsfcV" alt=""><figcaption><p>Sync files option to start the file scan</p></figcaption></figure>

You can cancel and then restart the scan.

<figure><img src="/files/SuA0s0iJ4BZszJmf6CQ0" alt=""><figcaption></figcaption></figure>

Based on the scan, Textual generates a list of the detected entity types with the number of values detected across all of the files.

<figure><img src="/files/ZY9XBER9wUUxfXazgGhJ" alt=""><figcaption><p>Detected entity types in the Textual item files</p></figcaption></figure>

## Previewing a file

To view the file content:

1. Click **Browse**.
2. Select the lakehouse where the source files are located.
3. In the source lakehouse, navigate to the file.

<figure><img src="/files/O8lm9d15dCaiX9zF0ccz" alt=""><figcaption><p>Content of an input file</p></figcaption></figure>

## Configuring entity type handling <a href="#entity-type-handling" id="entity-type-handling"></a>

On the **Entity types from scanned files** page, for each entity type, you configure how the detected values appear in the redacted files.

By default, the handling option is **Off**, which means that the values are not replaced, and remain as is in the output files.

The other options are:

* **Redaction -** Replaces each value with the name of the entity type, followed by a unique identifier for the value. For example, the name `John` is replaced with something like `[NAME_GIVEN_ab15c7]`.
* **Synthesis -** Replaces each value with a different realistic value. For example, the name `John` is replaced with `Michael`.

### Selecting the handling option for a specific entity type <a href="#handling-option-single" id="handling-option-single"></a>

To select the handling option for a specific entity type:

1. In the **Configuration** column, click the dropdown for the entity type.
2. From the dropdown list, select the handling option.

### Assigning the same handling option to all of the entity types <a href="#handling-option-multiple" id="handling-option-multiple"></a>

To assign the same handling option to all of the entity types:

1. Click **Bulk Edit Configuration**.

<figure><img src="/files/ovs4rVhc0gWj5XqZRsfG" alt=""><figcaption><p>Bulk Edit Configuration dropdown list to select the handling option for all of the entity types</p></figcaption></figure>

2. Select the handling option to assign.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tonic.ai/textual/textual-integrations/microsoft-fabric-integration/fabric-entity-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
