# July 7th

**Changelog released on 2025-07-07**

Welcome to the latest changelog. We fixed an UI issue when switching dashboards, corrected truncated reference text, improved reference sorting, sorted product structures by name, set global list default columns and fixed "Requires sorting" on global lists.

## Enhancement

1. **Disallow fixed list attribute type as template on list attribute:** This configuration is bad practice and should not be used. The ability to create is has been removed. A Global list value reference attribute with 'Allow multiple values' enabled shold be used instead. (SP-1309)
2. **Order of product structures is not sorted by name:** Product structures are now sorted alphabetically by name when choosing product structure on new products. (SP-1511)

## Bug

1. **Global list default columns if none are set by user:** The global list view now correctly has default columns. Before no columns were shown by default. (SP-1443)
2. **'Requires sorting' on global lists does not work:** The 'Requires sorting' option on global lists now correctly requires the user to sort newly added global list values on creation. (SP-1496)
3. **References sorting can be difficult:** Sorting references in an entity reference inputfield was not very clear and felt a bit random. (SP-1532)
4. **Text cut off in reference display:** Text would sometimes be cut off in entity reference inputfields that has a high amount of references. (SP-1533)
5. **Jumping between different dashboards quickly causes UI issue:** Switching between dashboards before they are fully loaded could cause an UI bug that would show all shared dashboards as the same in the left side menu. (SP-1564)


---

# Agent Instructions: 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:

```
GET https://docs.struct.com/changelog/july-2025/july-7th.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.