> 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/september-2026/september-30th.md).

# September 30th

**Changelog released on 2026-09-30** 

Welcome to our latest release! We’re excited to bring you powerful new feature enhancements alongside key system improvements and stability fixes. Highlights in this update include the ability to share custom view settings and set default list configurations per user group, expanded developer options for external widget apps, and enhanced business rule capabilities with string concantenation support. Additionally, we’ve resolved several issue areas—including data extraction integrations, case sensitivity during identifier lookups, asset upload behavior, and bulk translations—to ensure your workspace runs smoother and more reliably than ever.

## Enhancement

1. **Add default list configurations on user groups:** Default columns and filters can now be setup on user groups. Settings are available per entity type and catalogue. (SP-1539)
2. **Share created view settings with other users:** It is now possible to share view settings with other user marking them as shared when updating or creating a view setting. (SP-2658)
3. **Import creates duplicate items when a key column fails validation:** Improved import key validation to prevent duplicate values from being created. (SP-3156)
4. **Extensions: Expose Widget Uid and settings mode to external widget apps:**  Exposed the Widget Uid to external widgets apps. (SP-3180)
5. **Business rules: Let the Concatenate value format pattern use part of a value (substring):** Made it possible for the concatenate action to use substrings. (SP-3216)

## Bug

1. **Refresh top-bar page extensions after app changes:** Fixed issue where the top-bar page extension did not refresh correctly after app changes. (SP-3203)
2. **SortOrder on GlobalListValue is not updated correctly through .../globalLists/{uid}/values:** Fixed issue with SortOrder not being updated correctly through the /PUT global list value endpoint. (SP-3260)
3. **Data Extraction cannot fetch asset folders from external DAM:** Fixed issue that would occur if the user has an external DAM integration and tries to create a new data extractor. (SP-3274)
4. **Changing entity on category attributes does not reveal 'Save' button:** Fixed issue where changing the entity on category attribute did not activate the 'Save'-button. (SP-3283)
5. **Bulk translate does not save translated values on attributes in a list:** Fixed issue where bulk translations were not saved if the translated values were in a list. (SP-3284)
6. **Identifiers returns empty matches depending on casing:** Lookup on identifiers are now case insensitive and will not try to match both states. (SP-3300)

## Task

1. **Auto-number settings can be overridden by old API client:** Prevented the old API client from overriding auto-number settings. (SP-3153)
2. **Ensure asset upload do not fail on duplicate assets in folders:** Prevented the asset upload from failing more than one of the same assets are placed in the folder. (SP-3258)


---

# 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/september-2026/september-30th.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.