> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/release-information/connector-services/ifs-odata-connector/2.1.23.md).

# 2.1.23

2024-01-31

### New features

* Function operations that return collection of entities can now be configured with the same task configuration UI as the 'Read' operation. In practice this enables you to configure filters, limiting return data and so forth. It even enables you to start using $apply mode (where applicable) on function operations. There can be huge performance boosts to be gained here, so it is recommended to review function usage in your workflows.
* Support for 'Custom request' to send send binary/stream added. Using the 'Custom Request-operation', you can now post or patch binary data to an endpoint in IFS. Simply select content type "application/octet-stream" in the body tab and then select which variable containing binary data you want to send.
* Run with specific credentials if the client is 'Test Bench'. This feature requires either a new machine step, or a refreshed, for instance, re-mapped, machine step. Flow Studio needs to pick up additional details it did not have prior to this release. Any machine step configured with this release (or later) will be supported. 
* Run with specific credentials if the user is given machine user. Useful for instance if you have a scheduled workflow, but do not want to use a specific configuration for that scenario. You can keep the default authorization, let's say Open Id, but for machine user 'x', you want to use client credentials instead.
* Connector now runs on the .NET 8 runtime which improves the overall performance of connector.
* Refined communication log levels. You can now specify more levels of HTTP communication logging. Available options are   'None', 'Errors only' (default on new), 'Without payloads' and 'Truncated payloads'.  The recommended level is 'Errors only' where any non-successful call is logged (i.e. HTTP status code in 400- or 500-range). The payload is always logged on those calls.
* Communication logs can now be stored in a separate database from the rest of the connectors data. 
* Resize images returned from Media Library. Using a new operation, 'Download and scale media to file record', you can specify a scaling to be applied to the image before returning it to Flow. 

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FmlarYOvE7bgVt4k3dqbo%2Fimage.png?alt=media&amp;token=0ef46f1f-6596-4714-b9f4-8f0ad2ccf339" alt=""><figcaption><p>Scaling down with 50%</p></figcaption></figure>

* Entities returning collections of 'simple' values (i.e. enumeration or string values) are now better supported.
* Filtering on enumeration values in 'Read' operation is now easier to configure in the UI

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FwsGIL5zFHKKPLdxZVTfb%2Fimage.png?alt=media&amp;token=caace11b-7e18-4de1-8e6f-257e6dd382da" alt="" width="563"><figcaption><p>Enumeration members selectable in dialog</p></figcaption></figure>

### Bug fixes

* Fixed numerous bugs and performance issues regarding the communication log UI in connectors web UI.
* Fixed a bug where $count was not handled properly by 'Custom request' operation
* Fixed a bug where $expand was not handled properly by 'Custom request' operation
* Fixed a bug in 'Create and check in new document' via Document Library


---

# 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://help.novacuraflow.com/release-information/connector-services/ifs-odata-connector/2.1.23.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.