# 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.

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FFnwv7KdYtaHww1KVkIms%2F01%20Report%20model.png?alt=media)

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.

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FHqKcf9Fpxm6VxZ5eTZ7u%2F02%20not%20properly%20maintained.png?alt=media)

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.

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FCLT0rvIL22ADIbDi898k%2F03%20FV%20icon.png?alt=media)

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.

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FEh7C8GcyylTraGggfdP4%2F04%20Discrepencies.png?alt=media)

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.

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2F47ZkIP3etZyOxZqWSGG0%2F05%20traverse.png?alt=media)

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.

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2F0rpw4h73Mi9OBBiuEAl7%2F06%20Auto%20adjust.png?alt=media)

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.

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FFCQC9z8IHrQxpiHuVZJy%2F07%20verify%20check.png?alt=media)

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.

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FJB4DWkkkJePgpkpW1hfF%2F08%20uncheck.png?alt=media)

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.