> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/changelog/august-2026/august-3rd.md).

# August 3rd

**Changelog released on 2026-08-03**

Welcome to our latest changelog: data extraction asset fetching is more reliable, global search with the DAM extension no longer throw errors, identifier performance is optimized, and string-to-NumberAttribute imports now produce clearer errors.

## Bug

1. **Selecting sub-attributes in the AI command editor causes it to throw an exception due to duplicate keys.:** Fixed issue where the system would throw an exception during AI text generation due to the AI command having sub-attributes from the same complex attribute. (SP-2782)
2. **Global search error if using DAM extension:** (SP-2783)
3. **Dataextraction asset fetching is unreliable:** (SP-2784)

## Task

1. **Importing a string to a NumberAttribute that is used as key during global list import should give a more userfriendly error:** (SP-2263)
2. **Optimize identifier performance:** (SP-2780)


---

# 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.struct.com/changelog/august-2026/august-3rd.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.