> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/working-with-inforiver/15.-managing-inforiver-writeback-matrix-visuals.md).

# 15. Managing Inforiver Writeback Matrix visuals

In this section, we'll cover deployments and best practices while working with Inforiver Writeback Matrix visuals. 

**Inforiver deployments in Power BI pipeline setup:** Inforiver visuals can be migrated using Power BI pipelines. [Learn more](/working-with-inforiver/15.-managing-inforiver-writeback-matrix-visuals/inforiver-deployments-in-power-bi-pipeline-setup.md) about integrating Inforiver visuals with Power BI pipeline deployments.

**Safe procedures for copying Writeback Matrix visuals:** You may need to duplicate Inforiver visuals to reuse them across reports. [Learn more](/working-with-inforiver/15.-managing-inforiver-writeback-matrix-visuals/duplicating-writeback-matrix-visuals-best-practices.md) about duplicating Inforiver visuals and the safe procedures to ensure the visuals are copied without any issues.

**Recommended practices while working with Power BI desktop:** [Learn more](/working-with-inforiver/15.-managing-inforiver-writeback-matrix-visuals/recommended-practices-while-working-with-power-bi-desktop.md) about the best practices to be followed while editing Inforiver visuals from the Power BI desktop as well as from the Power BI service. 


---

# 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.inforiver.com/working-with-inforiver/15.-managing-inforiver-writeback-matrix-visuals.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.