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

# November 7th

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

Welcome to this changelog. We have fixed ‘Only Children’ filter for variant refs in list and complex attributes, resolved NullReferenceException on login, fixed DateTimeAttribute filter and more.

## Bug

1. **Query editor does not support dates like the search does:** The query editor now allows querying dates like column searches does.\
   (SP-1747)
2. **DateTimeAttribute filter issue:** Improved DateTimeAttribute search in advanced filter.\
   (SP-1903)
3. **NullReferenceException upon logging in.:** Login succeeds without errors, and widgets handle missing or null setup gracefully.\
   (SP-1926)
4. **'Only Children' not working on variant references in list- and complex attributes:** "Only Children" setting for VariantReferenceAttributes did not work when the the VariantReferenceAttribute was a subrule in a list or complex attribute.\
   (SP-1927)
5. **Clear tenant cache when changes to subscriptions or plans:** Tenant cache is now automatically cleared when changes are made to a tenants subscription or plan.\
   (SP-853)
6. **When saving a global list update elastic index:** Global list elastix index is now updated when saving a global list.\
   (SP-953)


---

# 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/november-2025/november-7th.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.