# Data Field Verification

Once data fields are created to extract data in Astera, the *Field Verification* option verifies if the data fields have been captured properly for all the data instances. It does so by checking if any non-blank character is present adjacent to the instances of data fields.

In this document, we will look at how to use *Field Verification* in a report model.

{% embed url="<https://youtu.be/nNJ9r5DZ5bE>" %}

## Using Field Verification

We have a report model with data regions and data fields defined.

![](/files/NLJtcW1hBRPMhXZkXo7C)

1. With this sample file, we can see that from row 28 onwards for the *Description* and *Quantity* columns, and row 22 onwards for the *Line\_Total* column, the data fields do not properly contain the data.

![](/files/vXQuS3eLi7kryJ66xfNx)

With files containing much larger amounts of data, it would not be possible to find such discrepancies.

2. With the data region selected, click on the *Start Field* *Verification* icon in the toolbar above the designer.

![](/files/sVIMTv5apmnRnw3Xav2r)

3. All the data fields having discrepancies in their data points are marked with a warning sign in the Model Layout panel for the selected data region. Field verification checks for any non-blank character adjacent to an instance for a data field to determine the discrepancy.

![](/files/dnyll476GRvf6hwU1GHs)

4. Select the data field *Description* and click on the *Previous* and *Next* icons in the toolbar above the designer to traverse among the discrepant instances for that particular data field.

![](/files/tZtg40gYbvgWF0w8TH73)

Astera also specifies where the discrepancy has occurred for each instance of the data field, below the designer.

5. You can click on the *Auto adjust all fields* icon on the toolbar above the designer to fix the discrepancies in the data fields for the selected region.

![](/files/S7tFURnV2M3V82Vm5UOI)

This option has adjusted the lengths of the data fields in the selected data region to contain the complete data in each data point.

{% hint style="info" %}
**Note:** In cases where two data fields are adjacent to one another, manually adjust the length of the data field to avoid inconsistencies.
{% endhint %}

6. *Field Verification* still gives warnings on row 29 for the *Unit\_Price* and *Line\_Total* fields.

![](/files/lDQmModL7JXo2aE2DqRQ)

It suggests that there is a non-blank character on the right of the *Unit\_Price* field. In this case, the character is part of the *Line\_Total* field.

7. We can uncheck the *Verify Right Boundary* option in the *Field Verification* section of the Field Properties panel for *Unit\_Price* and vice versa for *Line\_Total* and Astera will ignore the adjacent non-blank characters.

![](/files/MsS3KYxMocOsaPMI78ly)

These *Verify Left/Right Boundary* checkboxes allow the user to ignore the verification in cases when the adjacent character does not belong to the instance of a data field.

This concludes our discussion on how to use *Field Verification* in Astera.


---

# Agent Instructions: 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:

```
GET https://documentation.astera.com/report-model/use-cases/data-field-verification.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.