# OData Connector Log

### What?

The OData connector will transform the machine step configuration into REST API call in OData connector. The OData connector will also transform the response from IFS for the Flow server.

Result of the transformation, data sent to IFS and response from IFS can be viewed/investigated in Communication Log.

Whenever Flow app receives "odd errors" it might be useful to see what call was sent to IFS and what was the actual response. In rare cases transformation of the response may not succeed even though IFS returns OK, but flow is returned with an error.   

### How?

Calls can be inspected in two ways: 

1. Inspect all calls to selected projection 
2. Show all calls to all projections. 

Start by selecting connector configuration (= calls to which IFS Cloud configuration). 

Then either select projection (=endpoint) to inspect all calls to selected projection or check "Show logs from all endpoints"

List contains information about operation (GET, POST, DELETE, PATCH), execution time and status code from IFS.

Rows can be further filtered based on Sent, User, Method, Status Code column values.

<figure><img src="/files/Cfz3ALpcSgApv04ybbb5" alt=""><figcaption><p>Show log of selected projection</p></figcaption></figure>

<figure><img src="/files/M4mtNaiuCP0ayqZq3kT0" alt=""><figcaption><p>Show log of all calls</p></figcaption></figure>

### Inspecting result

When selecting a single call both the request to IFS and response from IFS can be inspected in different tabs.

<figure><img src="/files/T35dPm0gRkrmWK4BLA8a" alt=""><figcaption></figcaption></figure>

### Overview

Request: transformed REST call

Status Code: HTTP response code from IFS

Duration: execution time of the call

<figure><img src="/files/8P0NCMez7euhggmVdU5r" alt=""><figcaption><p>Read operation overview</p></figcaption></figure>

### Parameters

This tab shows data sent to IFS as request parameters, applies to Read operation only.&#x20;

Selected attributes and conditions defined in flow transformed to OData query syntax.

<figure><img src="/files/vd38N3mfd0kqyNX41Djk" alt=""><figcaption><p>Read parameters</p></figcaption></figure>

### Request Body

This tab shows data sent to IFS in request body (=payload) in POST (Create, Action), PATCH (Update) or batch operations. This data is inserted viaInput tab in machine step in Flow.

<figure><img src="/files/edmnK8YwHBf9iD8MqdqI" alt=""><figcaption><p>Payload if Create operation</p></figcaption></figure>

When executing batch operations, for example adding two tasks to a Work Order with `PrepareWorkOrderHandling/ActiveSeparate/WorkTaskeArray/Batch Add to WorkTaskeArray` operation, request body contains all individual calls sent in one call to IFS and each call payload is presented as string within each call.

<figure><img src="/files/cNU3R3sawpSGDQ39b2dv" alt=""><figcaption><p>Individual call (green) and payload of each call (yellow)</p></figcaption></figure>

### Response

In case operations return data (all CRUD operations), this can be inspected in Response tab. Returned values can be selected in Output or Select tabs in machine step in Flow.

<figure><img src="/files/8JpjhezPm0STDjioMvzs" alt=""><figcaption></figcaption></figure>

### Request/Response Header

"Request header"-tab contains OData connector generated REST call headers and "Response header"-tab contains the IFS response headers.


---

# Agent Instructions: 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:

```
GET https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/debugging-and-testing/odata-connector-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.