> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/desktop-client/reporting/invalid-references.md).

# Invalid References

The aqua report designer allows you to reference data fields in a lot of different places (report bands, charts, expressions which control styling or visibility, etc.). In some cases, it can happen that the report designer is not able to resolve such references anymore. One possible reason is that a calculated field has been renamed and the references to it in one or more charts were not updated. aqua will try to automatically remove such invalid references. In this case, you will see a warning like this:  

<figure><img src="http://aquawiki.andagon.com/pictures/drex_invalid_references_custom.png" alt=""><figcaption></figcaption></figure>

aqua has automatically removed the invalid references. Before you generate the report again, you should review the places mentioned in the error message and correct the references. In some rare cases, aqua might not be able to remove the references. In this case, you will see the following error message: &#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_invalid_references_custom_2.png" alt=""><figcaption></figcaption></figure>

Please contact the aqua support team in such a case and provide us the exported report template.&#x20;

{% hint style="info" %}
We are currently aware of the following known issue: the aforementioned warnings might appear for reports which still use the old data binding mode. When you open a report after this warning has been shown, make sure to convert it to the new expression binding mode. The report designer will ask you to do this when the report designer is opened.
{% 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 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.aqua-cloud.io/documentation/desktop-client/reporting/invalid-references.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.