> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/rf/en/getting-started/configure-rf/display-receipts-from-record.md).

# Display the list of receipts from your context

You can create a custom link from the tax receipt to your original main object, so you can quickly get back to your context once the document is generated, using a flow.

## Create a lookup to the tax receipt

* From Salesforce Setup, go to Object Manager
* On your main object, from which you create the tax receipt, create a new Lookup Relationship field to the tax receipt
* Add it to your page

## Create a field update flow

* From Salesforce Setup, go to Flows
* Create a flow triggered when a record is created on the Tax Receipt object (`gnx_Tax_Receipt__c`)
* Optimize the flow for "Actions and Related Records"
* Add an Update Records element
* Name it as you like
* For how to find records to update, select "Use the tax receipt record that triggered the flow"
* Set the condition requirements to None
* Set the field values for the Tax Receipt record: Don\_\_c with the tax receipt Context Id value: $Record > Context Id
* Save and activate


---

# 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://university.gonexa.fr/rf/en/getting-started/configure-rf/display-receipts-from-record.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.