> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-us/verifone-hq/vhq-parameter-management/configuring-parameter-templates/parameter-template-pt-support-for-multi-record-parameters/applying-parameter-template-to-the-device.md).
# Applying parameter template to the device
Apply parameter templates to devices in VHQ with options to override or append parameter values for both base-level and multi-record parameters.
{% hint style="info" %}
**Use this when** you need to apply a configured parameter template to a specific device.
{% endhint %}
The parameter template must already be configured in the Application Library. Once created, the **Template** button activates on the *Device Profile* screen's *Parameters* tab.
{% hint style="info" %}
The package must be assigned to the device before you can apply the parameter template.
{% endhint %}
## Find the device
Search for the device on the *Device Search* screen using the application name and version, or search by device model in the *Download Library* screen's *Package Name* field (the source package name listed in the Application Library for the configured template). You must perform a device search to apply a template.
## Apply the template
{% stepper %}
{% step %}
### Open the Parameters tab
Select the device, go to *Device Profile*, then **Device Details** > **Parameters**, select the application, and click the **Templates** icon. Only one template can be applied to a device at a time.
{% endstep %}
{% step %}
### Choose override or append
VHQ provides an **Override Parameters Value** checkbox:
* **Selected**: Clears all parameters currently applied to the device and replaces them with the template's values. For base-level parameters, only the values in the template are applied; others remain intact. For multi-instance parameters, existing instances are overridden with the template's instances — if a parameter isn't found in an instance, VHQ restores it to the default value.
* **Unselected**: Retains existing instances and adds any from the template that don't already exist on the device. If an instance exists on both, only that instance is overridden.
{% endstep %}
{% step %}
### Apply
Select the template, choose whether to override, and click **Apply**. VHQ confirms: *The parameter values will be overridden. Do you want to continue?* Select **Yes** to apply, or **No** to cancel.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
**Example**: App1 has base-level parameters P1–P10. Template PT1 defines P1 and P5. Applying PT1 with override copies only P1 and P5 from the template; the rest restore to default values.
{% endhint %}
## Guidelines
* You can edit instances and parameter values directly from the *Device Profile* screen — click the pencil icon, edit, and **Save**. The parameters update and activate immediately.
* You cannot edit the parameter template itself from *Device Profile* — only from *Application Library*. After editing there, you must reapply the template to see the updated values on the device.
* If the *Parameters* tab lists no applications, assign a software package first: click **Software Assignment** on *Device Profile*, set *Assignment type* to **Package**, select the package, and click **Save**.
* When a template with ADKH4 format is applied (from *Device Search* or *Device Profile*), all parameters with source type *Template* display as *User* in the UI.
Keywords
Also called: apply parameter template, override parameters value. Search terms: append parameters, base level parameters, multi level parameters.
---
# 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.verifone.com/support-us/verifone-hq/vhq-parameter-management/configuring-parameter-templates/parameter-template-pt-support-for-multi-record-parameters/applying-parameter-template-to-the-device.md?ask=&goal=
```
`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.
