> 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/mrpeasy/release-history.md).

# Release History

***

### V1.28

#### Created: 2026-02-02

* Implemented aggregation for child stream records with duplicate keys

***

### V1.27

#### Created: 2025-12-11

* addded additional user activities for stock\_lots

***

### V1.26

#### Created: 2025-12-08

* removed user actions activities relating to comments as the object\_id doesnt releate to the parent object

***

### V1.25

#### Created: 2025-12-05

* ensured user actions which releate to deleted items get enqueued as delete records

***

### V1.24

#### Created: 2025-12-04

* fixed issue around incremental syncs

***

### V1.23

#### Created: 2025-12-03

* bump version numbers
* refactored codebase for maintainability
* updated codebase to allow for checkpointing
* modified how the user actions are utilized for incremental runs, so all dates are now kept in Unix timestamp format
* reworked how deletes for incremental runs are processed

***

### V1.21

#### Created: 2025-10-06

* correct description field type for author in MO Notes
* correct service\_order\_code data typr for RMA Orders

***

### V1.20

#### Created: 2025-09-24

* modified the next start date to have a day offset due to not all records being available in the user\_actions when running a sync

***

### V1.19

#### Created: 2025-07-02

* updated runtime versions
* fixed schema datatype issue for Manufacturing Order Operation Workstations

***

### V1.18

#### Created: 2025-06-17

* removed whitespace from user\_actions user\_id column

***

### V1.17

#### Created: 2025-03-05

* Fix author field type in API schema definition

***

### V1.16

#### Created: 2025-03-02

* bumped version numbers
* refactored to take into account parent / child stream relationships
* removed omnata\_sync\_id, snapshot\_id and snapshot\_index as using latest sync engine these are no longer required for child objects
* added ability to run concurrent streams

***

### V1.15

#### Created: 2024-08-02

* ignore 404 results when invalid data is returned from audit
* bumped runtime version

***

### V1.14

#### Created: 2024-04-02

* Bump plugin runtime version
* Built with omnata-plugin-devkit==0.3.17 which includes pinned stored proc dependencies

***

### V1.13

#### Created: 2024-03-21

Added index to the shipment products as shipment product element doesn't have to be unique in MRPeasy and there is no key available for the shipment product

***

### V1.12

#### Created: 2024-03-20

Update plugin runtime to latest version

***

### V1.11

#### Created: 2024-03-19

Add 'lot\_id' to sync\_id\_fields in shipment\_products schema

***

### V1.10

#### Created: 2024-03-18

Fix data type and description for stock lot locations

***

### V1.9

#### Created: 2024-03-13

Fixed issue where the manufacturing\_orders inbound stream data incorrectly included the 1470 activity code

***

### V1.7

#### Created: 2024-03-08

Switched to new plugin-oriented billing mechanism

***


---

# 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/mrpeasy/release-history.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.