> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/debugging-and-testing/aurena-debugging/inspect-in-web-browser.md). # Inspect in web browser ### Opening the inspect console Built into the web browser Chrome there's a tool to inspect web pages. Other browser have similar tools. You can access the console on any web page via **RMB-> Inspect** or by pressing "**ctrl+shit+i**". This will open the inspect console within the web browser. {% hint style="info" %} If you open the inspect console for the first time it is probably horizontally docked. Docking it vertically will improve readability. {% endhint %}

Dock the inspect console to the browser bottom

### Inspect HTTP calls The inspect console contains a lot of functionality but we are interested in the **Network** tab, and then select "**Fetch/XHR**". Now that we are ready to capture network activity perform the action in IFS that you want to inspect.

In this example the Customer page is used. Navigate to the Customer page in Aurena and clear the Inspect Console log. Then select a customer in the record selector in IFS. This will generate a set of OData requests. Depending on where you navigate or what action you perform, there can be many requests to and from the IFS backend. The amount of requests might feel overwhelming at first but you will quickly learn what to look for.

Each Projection have a main Entity Set which is the root entity within a Projection. In this example the Entity set is called **CustomerInfoSet**. Those who are familiar with the logical units in IFS will recognize the OData entity namnings.

When selecting a line in the request list the requests details pane will open, revealing additional tabs related to the request. The **Headers** tab will contain Header parameters of the request, such as Request URL , Request Method and Status Code**.** The Requests Method is important when looking for a specific request in the list. E.g when saving data, the Request Method will instead be POST or PATCH. In addition to the **Headers** tab in the details also has tabs for **Payload**, and **Response**. Selecting the Payload tab will reveal the request payload sent. There's not payload for GET requests but Chrome will display the query string parameters of the URL.

In Response tab the JSON response can be found. It's not formatted at this point and hard to read. RMB -> "Open in new tab". If you installed the recommended extension in the [Useful Applications](/flow-ifs-cloud-development-guidelines/getting-started/useful-applications.md) section, a formatted JSON will open in a new tab. The JSON can of course be copied and viewed in any code editor.

The same procedure is used to inspect the rest of the CRUD operations. Below is an example where a field is updated.

--- # 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.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/debugging-and-testing/aurena-debugging/inspect-in-web-browser.md?ask=&goal= ``` `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.