# Nightly build October 27, 2026

> Nightly build October 27, 2026: You can now link straight to a component in the App Designer. Add `?open=<Type>:<id>` to the App Designer URL (for example…

Source: https://www.fuuz.com/resources/nightly/2026-10-27

Nightly build


Today's changes improve Flow Designer performance, make data model deployment safer, and add a way to open a component directly in the App Designer. 3 changes. Pre-release.

[All nightly builds](https://www.fuuz.com/resources/nightly/) [Subscribe](https://www.fuuz.com/resources/nightly/#subscribe)

**Pre-release.** Nightly builds run in our nightly environment for testing and early feedback. Changes here can be revised or held back, and nothing on this page is a commitment for the next production release. For what is generally available, see [production releases](https://www.fuuz.com/resources/release-notes).
**AI generated.** These notes are written by AI from the build's changes, and AI sometimes gets things wrong. If you have questions, please contact us through [Fuuz customer support](https://support.fuuz.com/).

Build

2026-10-27 nightly

Date

Oct 27, 2026

Environment

Nightly

Changes

3

### Improved

- You can now link straight to a component in the App Designer. Add `?open=<Type>:<id>` to the App Designer URL (for example, `?open=DataFlow:myDataFlowId`) and that component opens in the workspace. If the value is unknown or malformed, the designer opens on its normal start page.

### Fixed

- The Data Flow Designer no longer sends a stream of repeated requests from Data Changes nodes while you edit a flow. Flows with many Data Changes nodes should now stay responsive and put much less load on the application service. Log node level indicators still update as before.
- A data model can no longer be deployed if its `id` field has no `unique` setting. Deployment now rejects the model with a validation error. Before this fix, models like this could get through and break the application build.
