> 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/bulk-update-parameters-across-device-instances.md).

# Bulk update parameters across device instances

Update a parameter across all application instances for selected devices in VHQ.

{% hint style="info" %}
**Use this when** you need to update one parameter's value across every instance on a set of devices, without visiting each instance individually.
{% endhint %}

A checkbox, **Update parameters across all instances**, on the *Edit Parameter for Application* screen lets you bulk-update an existing parameter across every instance on selected devices. It's unselected by default. This only supports editing values — you can't add, delete, or reorder instances with it. Updating a value in one place updates it throughout all instances for all selected devices.

This works in both the *Device Search* and *Device Profile* screens. On save, VHQ shows *Parameters successfully updated*. Returning to this screen later, the previously entered values are no longer shown.

{% hint style="info" %}
**Example**: Hundreds or thousands of card ranges may be configured across multiple devices. Among many CardRange instances, a parameter like *PAN High* or *PAN Low* may be common. Instead of visiting every instance individually, you can update it once and have the value applied throughout all instances on all selected devices.
{% endhint %}

## Update a parameter across instances

{% stepper %}
{% step %}

### Select the devices

On *Device Search*, select the devices and click **Edit Parameters**.

<figure><img src="https://verifone.cloud/sites/default/files/inline-images/1_26.jpg" alt="Select devices"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Click Edit

On the *Edit Parameters for Application* screen, click **Edit**.

<figure><img src="https://verifone.cloud/sites/default/files/inline-images/2_9.jpg" alt="Edit Parameters for Application"><figcaption></figcaption></figure>

<figure><img src="https://verifone.cloud/sites/default/files/inline-images/3_4.jpg" alt="Edit screen detail"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select the bulk-update checkbox

**Update parameters across all instances** appears, unselected by default.

<figure><img src="https://verifone.cloud/sites/default/files/inline-images/4_1.jpg" alt="Update parameters across all instances checkbox"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Update and save

Select the checkbox, update the parameter, and click **Save**. The value updates across all instances for all selected devices.

<figure><img src="https://verifone.cloud/sites/default/files/inline-images/5_1.jpg" alt="Saved bulk update"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

<details>

<summary>Keywords</summary>

Also called: bulk parameter update, update across instances.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/support-us/verifone-hq/vhq-parameter-management/configuring-parameter-templates/parameter-template-pt-support-for-multi-record-parameters/bulk-update-parameters-across-device-instances.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
