> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-5.6/vizpads-explore/swapping-business-view-of-charts/swapping-only-the-current-vizpad.md).
# Swapping only the current Vizpad
Steps to swap the current Vizpad being worked on
1. Click on **Apply only to the current Vizpad** if you want the swapping to happen to all the tabs in the current Vizpad.
2. Click on **Apply only to the current tab** if you want the swapping to happen only to the current tab.
3. Click on **Apply** to apply swapping, or click on **Cancel** to dismiss the window.
Swapping only the current tab
4. If the swapping has been done successfully, the following message will be displayed at the bottom.
Message indicating the successful swap
{% hint style="warning" %}
Please note that after clicking on "**Apply**", the swapping of Business Views will be configured, but will not be effective immediately. For more details, check out [this page](/tellius-5.6/vizpads-explore/swapping-business-view-of-charts/configuring-the-time-of-swap.md).
{% endhint %}
---
# 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://help.tellius.com/tellius-5.6/vizpads-explore/swapping-business-view-of-charts/swapping-only-the-current-vizpad.md?ask=&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.
