> 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/may-2025/may-26th.md).

# May 26th

**Changelog released on 2025-05-26**

Welcome to this update. We fixed v3 upgrade transaction errors, advanced queries in product catalogue, PowerPoint thumbnails, enrichment scope resets, private searches on shared dashboards, product views and filters, API null variantconfig and variantgroupconfig, multirow input height, task dashboard headlines, translations and workflow modal hangs.

## Bug

1. **Missing translations:** (SP-1328)
2. **Task dashboard widget does not display correct headline:** (SP-1340)
3. **'Input height (px)' on Multirow text attribute does not work:** (SP-1349)
4. **Variantconfig and variantgroupconfig is allowed to be null when set from the API:** (SP-1350)
5. **Product structure filter should be checkboxes instead of a text field:** (SP-1353)
6. **Issues with "Product attribute view" on variants:** (SP-1356)
7. **Private saved searches should not be available to use on shared dashboards:** (SP-1361)
8. **Enrichment attribute scope reverts to "all" when editing enrichment rules:** (SP-1363)
9. **Powerpoint files are not displayed with thumbnails when added to a product:** (SP-1364)
10. **Advanced query in product catalogue view does not persist:** (SP-1368)
11. **Transaction error when upgrading from v3:** (SP-1369)
12. **Change workflow modal "hangs" when stopped by a business rule:** (SP-704)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.struct.com/changelog/may-2025/may-26th.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.