> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/utilities/data-parametrization.md).

# Data Parametrization

Data parametrization in Avo Assure allows you to create flexible test scripts by replacing hardcoded values with variables. This enables the reuse of the same test script with different inputs, enhancing test coverage, flexibility, efficiency, and scalability.

### This document includes:

**Prerequisites**

The pre-requisites to follow for performing Data Parametrization

**Ways to Achieve Data Parametrization**

Different ways to perform data parametrization in Avo Assure

### Pre-requisites

1. Avo Assure Client must be installed and connected with Avo Assure 
2. Excel sheet/Data Table should be created 
3. Ensure Excel path/Data Table path is ready for access 

### Ways to Achieve Data Parametrization

In Avo Assure, there are two different ways to achieve Data Parametrization:

1. [Through Excel Sheet](/avo-assure/utilities/data-parametrization/through-excel-sheet.md) 
2. [Through Data Table ](/avo-assure/utilities/data-parametrization/through-data-table.md)


---

# 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.avoautomation.com/avo-assure/utilities/data-parametrization.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.