> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/inquiries-and-reports.md).

# Inquiries and reports

In the Inquiries and reports, an administrator is able to view all reports generated by the Raptor module (Modules > 9A Raptor DWH > Inquiries and reports).

## HTTP Logging

#### HTTP logging overview

HTTP logging is a valuable tool for monitoring and troubleshooting the details of HTTP requests and responses between the D365 F\&O server and external web services (such as 9A Raptor DWH).

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-e9defc968c591d13f3bb5386c96a399c6daebe00%2Fimage%20(276).png?alt=media" alt=""><figcaption></figcaption></figure>

#### HTTP logging features

The following information is captured by HTTP logging:

| Captured field       | Meaning                                                                                   |
| -------------------- | ----------------------------------------------------------------------------------------- |
| **Timestamp**        | Date and time when the request was made.                                                  |
| **Module**           | Initiating module, such as Document Management, Output Management, or Process Management. |
| **Internet Address** | External web server being called.                                                         |
| **Endpoint**         | Specific URL or endpoint being accessed.                                                  |
| **Method**           | HTTP request type, such as GET or POST.                                                   |
| **Content Type**     | Data format, such as JSON or XML.                                                         |
| **HTTP Status Code** | Server response code, such as 200 = OK, 401 = Unauthorized, or 404 = Not Found.           |
| **Parameters**       | Parameters included in the HTTP request.                                                  |
| **Content**          | Content of the HTTP response.                                                             |

#### How to access HTTP logging

1. Navigate to **9A Raptor DWH** > **Inquiries and Reports** > **HTTP Logging**.
2. Ensure that HTTP logging is enabled by setting the parameter in **9A Raptor DWH parameters** under the **General** tab.

<div align="left"><figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-e56d91132753693a3a01dc8c06e86b15f645f5d8%2Fimage%20(275).png?alt=media" alt=""><figcaption></figcaption></figure></div>

{% hint style="warning" %}
**Activate with caution**: The HTTP logging parameter should only be enabled in non-production environments or, if necessary, in production environments for a limited time. Enabling this feature for extended periods can cause the logging table to grow rapidly, leading to potential performance issues.
{% endhint %}

### Context logging

With the HTTP logging setting activated, you can also view the context data passed from D365 F\&O to the Document Warehouse. This logging can be accessed by clicking the "dino" icon on a specific form. It allows you to examine which field values are being transferred, making it easier to troubleshoot issues.

This feature is particularly helpful for problem-solving, as it provides clear visibility into the data being passed. This makes identifying potential root causes much easier.

## Report logging

Report logging is a helpful tool for validating the parameters used during report generation and analyzing the duration of key processes, such as XML generation, external web service calls, and report completion.

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-31e68d31c378a9552ea7e94cd0e84b60daed9fef%2Fimage%20(277).png?alt=media" alt=""><figcaption></figcaption></figure>

#### Features of Report Logging

The following features are available with report logging:

* **Download XML File**: If an XML file is generated, it can be downloaded for review.
* **View Print Settings**: You can view the current print settings used for the report.
* **View Log Messages**: Access log messages for troubleshooting and analysis.

#### How to Access Report Logging

1. Navigate to **9A Raptor DWH** > **Inquiries and Reports** > **Output Management** > **Report Logging**.
2. Ensure that report logging is enabled by setting the parameter in **9A Raptor DWH parameters**, under the **Output Management** tab.

<figure><img src="https://1567270722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbMdBZV3cNP56k0aYYCI6%2Fuploads%2Fgit-blob-109c4aa99c6072f244b290299f1a61f258090abb%2Fimage%20(278).png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
The report logging parameter should only be enabled in non-production environments or, if necessary, in production environments for a short period. Keeping it active for extended periods can cause the logging table to grow quickly, potentially impacting performance.
{% 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://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/inquiries-and-reports.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.
