# Line Count

*Line Count* option in Astera enables users to specify the number of lines over which a data region spans. This feature is useful when transposing data that appear in rows in an unstructured file and converting it into vertical fields (columns) inside a report model.

In this document, we will explore how the *Line Count* feature helps with the selection of a data region in Astera.

## **Sample Use-Case**

In this case, we have unstructured data in a PDF file.

Download the sample PDF file here.

{% file src="/files/PHKLjdoQ9W9U63jkxarS" %}

![](/files/M6Uznlt1DxoYqV0f79ud)

This file contains a customer list report including their account name, contact, and address details.

You can see that a single record spans over 4 lines on this PDF file. In order to capture this data and place it into different fields, we will use the *Line Count* feature.

First, let’s load this unstructured file onto the Report Model designer.

1. Go to *File > New > Report Model* and select the source file from your directory.

![](/files/ahtCE9MZj6nRKn2z2VME)

There are many options available in the *Report Options* panel to configure how Astera reads the unstructured PDF file such as specifying the scaling factor, font, tab size, and password.

You can read about these options here.

2. Click *OK* and the source file will open on the designer.

![](/files/UKu1L5xyY2Dd6WcBRiPC)

Now that we have loaded the source file in Astera, let’s create an extraction template.

## **Creating a Report Model**

1. Right-click on the *Record* node under the Model layout panel, and select *Add Data Region* from the context menu.

![](/files/xyZ3RLv9GR7uOmJ63uil)

A pattern-matching bar and *Region Properties* panel will appear and a *Data* node will be added under the *Record* node in the *Model Layout* panel.

![](/files/2XbPKJBH1HXKBi1Mcq6S)

2. Specify a pattern with which Astera can match your source file to capture the desired data. You can use an alphabet, character, number, word, wild card, or any combination of these to define your pattern.

In this case, write “ACCOUNT” in the pattern-matching bar as shown below.

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

You can see that only one field of information is captured through the matching pattern. In order to capture the data spanning over 4 lines, we must increase the *Line Count* to 4.

3. Increase the *Line Count* value to 4 from the *Region Properties* panel.

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

Each data region block contains information of a single record. Let’s create data fields.

4. Highlight the data region after “ACCOUNT:”, right-click on it, and select *Add Data Field* from the context menu. Rename it to *Account*.

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

5. Repeat the process to create more data fields. You can see the layout of the extraction template in the Model Layout panel.

<figure><img src="/files/8RC28C59aL7BfmixI1Ae" alt=""><figcaption></figcaption></figure>

6. You can preview data by clicking on the *Preview Data* icon placed in the toolbar at the top of the designer window.

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

A *Data Preview* window will open displaying a preview of the extracted data.

<figure><img src="/files/2wL7CXsVH3774Noz8HGG" alt=""><figcaption></figcaption></figure>

This concludes using the *Line Count* option while building an extraction template in Astera. The source file for the use case discussed above is attached below.


---

# 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/astera-data-stack-v8/report-model/use-cases/line-count.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.
