# Delimited Parser

The *Delimited Parser* in Astera reads and processes a single stream of text in delimited format as input and returns its elements as parsed output. It enables users to transform an otherwise semi-structured data into a structured format.

In this document, we will learn to use the *Delimited Parser* to parse an incoming text stream in Astera.

### Use Case

In this case, we are using the *Delimited File Source* to extract our source data. You can download this sample data from the following link:

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

![](/files/e4Gj8cVHpNrvfWuBatI9)

The source file contains customers’ contact information including their name, address, postal code, phone number, etc.

![](/files/3vfFWJJGLNHVOtUlbEOb)

Upon previewing the data, you can see that it is difficult to decipher fields and elements since the data is in a single text stream with fields and records separated by delimiters. To make sense of this data, each records needs to be parsed into its elements in respective fields.

To do this, we will use the *Delimited Parser* object.

#### Using Delimited Parser

1. To get the *Delimited Parser* object, go to *Toolbox > Text Processors > Delimited Parser* and drag-and-drop the object onto the designer.

![](/files/8rzaCFQci4omEWRFkN1c)

You can see that the dragged object contains a single *Text* field.

2. Map the *Customer\_Info* field inside the source object onto the *Text* field inside *DelimitedParser* object.

![](/files/nvNa0sbgBstAMt7MSVkn)

3. Right-click on the object’s header and select *Properties*.

![](/files/2mOurZTQ7TXNSeuzG7mg)

A configuration window will open as shown below.

![](/files/s8AEJo5sZXnQQ7eT3ANz)

Let’s look at the properties on this window.

* *Parse Data Pattern* – Contains three patterns in which the dataset can be parsed:

  ![](/files/nEtQEBEcuNVD6mnnSARx)

  * *Single Record* – Data is parsed into a single record with multiple fields. Users need to provide a field delimiter, and a text qualifier, if necessary.
  * *Multiple Records* – Data is parsed into multiple records with a single or multiple fields. Users need to provide a field delimiter as well as a record delimiter.
  * *Field Arrays* – Data is parsed into an array of records and fields. Users need to provide a field value delimiter and an array separator.

The source data in this case contains multiple records with many different fields. Therefore, we will set the *Parse Data Pattern* option to *Multiple Records.*

4. Provide a *Field Delimiter* and a *Record Delimiter*. The source file also contains a *Text Qualifier*.

![](/files/gCddVQMegDNte6UVS0sW)

Click *Next.* This is the *Layout Builder* screen.

![](/files/deooxIdTo2zlvIz0Ed57)

5. Here, write the names of the fields that you want to create.

![](/files/woI6T02rpvAFZpVrSHES)

Click *OK.* The *Delimited Parser* object now has new fields in the *Output* node.

![](/files/cinyNcctVWiEEbZOWwPl)

To preview data, right-click on the object’s header and select *Preview Output* from the context menu.

![](/files/rdmC8MvJPQ2oNcsvpg1T)

A *Data Preview* window will open. Upon expanding the records, you can view the parsed output.

![](/files/1Mb1AOBabd928zLthSdx)

To store this parsed output, you can write it to a destination file or use it for some transformation further in the dataflow.

This concludes using the *Delimited Parser* 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/dataflows/text-processors/delimited-parser.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.