> For the complete documentation index, see [llms.txt](https://docs.omnata.com/omnata-product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/apps/microsoft-dynamics-365-business-central/release-history-1.md).

# Release History

***

### V2.0

#### Created: 2026-06-05

* Enhance stream name uniqueness handling and add tests for deduplication logic

***

### V1.15

#### Created: 2026-04-09

* modified sync runs so that if there is an error for a single company the remaining companies can still complete

***

### V1.14

#### Created: 2026-03-24

Improve handling of internal when processing empty responses

***

### V1.13

#### Created: 2026-03-20

* Improve handling of internal when processing empty responses
* bumped version numbers

***

### V1.12

#### Created: 2025-10-20

* fixed issue with loading the stream list
* added logic to prevent a stream from failing if an expansion property api can't be found.

***

### V1.11

#### Created: 2025-08-19

* bump plugin dependencies
* fixed api lookup for OData when there are no dependancies found

***

### V1.10

#### Created: 2025-05-26

* ensured expansion items are only returned if the corresponding stream exists

***

### V1.9

#### Created: 2025-05-22

* bumped runtime version numbers
* modified state so dates are stored as strings

***

### V1.8

#### Created: 2025-05-22

* bumped runtime version numbers

***

### V1.7

#### Created: 2025-05-21

* bumped omnata-plugin-runtime version
* refactored how data is retreived due to never ending syncs under certain conditions
* expected totals are now retreived at the start of a run to determine if the run is required or not
* ensured when a child stream isn't selected, the expanded properties are not obtained
* modified state to show expected and retrieved record counts
* modified full refresh of data not to be date based

***

### V1.6

#### Created: 2025-04-11

added in additional udf so that you can get a table count

***

### V1.5

#### Created: 2025-03-24

* updated vendor\_payments to ignore applyVendorEntries expansion
* updated how requests are made via the session to reduce issues around the exception "Failed to establish a new connection" when making an api call
* bumped version numbers for omnata-plugin-runtime and devkit

***

### V1.4

#### Created: 2025-03-13

* removed connection method 'OAuth (Microsoft Entra)'

***

### V1.3

#### Created: 2025-03-04

* update readme to include additional required API application permissions
* updated OData Sync's to have company\_id added to the output instead of the company\_name for consistency across the different type of api calls.

***

### V1.2

#### Created: 2025-03-02

* fixed issue when cursor field was just a date instead of datetime caused exception being incremented

***

### V1.1

#### Created: 2025-02-21

* refactor environment handling
* removed environment check from initial connection test

***

### V1.0

#### Created: 2025-02-12

* added api/v2.0 endpoints
* added OData endpoints
* added custom endpoints
* added direct query capabilities

***


---

# 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.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/apps/microsoft-dynamics-365-business-central/release-history-1.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.