> For the complete documentation index, see [llms.txt](https://docs.tracr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tracr.com/release-notes/tracr-1.7.0.md).

# tracr 1.7.0

## Tracr Portal Release Notes

* Fixed an issue with selecting and sorting diamonds in the Inventory page.
* Added the ability for integration events on the Monitoring page to be filtered for diamonds with "Error" status.
* Improvements to Inventory screen user interface.
* Fixed discrepancies between the number of images on the Inventory screen and the Diamond Experience.
* Added box ID checks against sight year and number when uploading a CSV via the Diamond Integration Tool (see note below).
* Improvements to UI consistency.

## Tracr API Release Notes

* Added box ID checks against sight year and number when creating a diamond via the API (see note below).

{% hint style="info" %}
Note on box checks

In addition to box ID, the Tracr API and Diamond Integration Tool now check sight year and sight number when verifying a diamond’s box on upload.

A diamond which has a valid box ID but an incorrect corresponding sight year and/or number will be rejected. In addition to the existing checks, a diamond can now only be added to the inventory if these fields align.
{% 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 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.tracr.com/release-notes/tracr-1.7.0.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.