# FUSE RC29 build 1 for Windows

This guide covers the Windows 11 x64 browser portable, version 1.0.0-rc.29-build.1. RC29 updates the portable only. Native EXE/MSI downloads remain on RC28 (1.0.28); the Microsoft Store listing retains its own version.

## Download and start

Download: https://github.com/anandvegaraju/FUSE-Downloads/releases/download/v1.0.0-rc.29-build.1/FUSE-1.0.0-rc.29-build.1-windows-x64-browser-portable.zip

- Size: 43,767,090 bytes.
- SHA-256: `70983bc13f2f4c74ca563f850ff6015b9da20f1aa0771320d2c1606985bed4be`.
- Checksum file: https://github.com/anandvegaraju/FUSE-Downloads/releases/download/v1.0.0-rc.29-build.1/FUSE-1.0.0-rc.29-build.1-windows-x64-browser-portable.sha256.txt

The direct download is unsigned. Windows or your organisation may block it. Follow your organisation's policy and ask your administrator if needed. A matching checksum confirms file integrity, not publisher trust.

1. Close the older FUSE window and its console.
2. Extract the whole ZIP into a new writable folder. Keep all its files together.
3. Open **Start FUSE.cmd**. The Windows Node runtime is included. Edge or Chrome is recommended; PowerShell must be available for the private launch file, saved passwords and file dialogs.
4. For a desktop shortcut, run **Create FUSE shortcut.cmd** once. Recreate it if the extracted folder moves.
5. Before closing, wait for **Workspace saved**, close the app window, then close the console. Run one portable copy at a time.

Preserve `%LOCALAPPDATA%\FUSE SQL Studio\browser-portable` and your SQL files when upgrading. Saved passwords are protected for the same Windows account using Windows DPAPI. Other workspace data and local documents are not encrypted by FUSE. Installed and portable editions keep separate workspaces.

Use authorised non-production environments. Add your Fusion connection, choose HCM or Financials / SCM, and select **Save & test**. Review paths under **Advanced** with your report owner. Setup can create missing FUSE BI Publisher files; it does not overwrite existing models or grant database privileges.

## Workspaces, tabs and recovery

Use the workspace selector above the editor to group drafts by task. Each workspace remembers a default connection, active tab and Write, Review or Investigate layout. Search open tabs by full title, pin frequent drafts, drag to reorder, or use the optional vertical list. Move a draft between workspaces through its tab actions.

Recent revisions and closed tabs restore as new unsaved copies. Recovery is bounded to 80 revisions, 10 per draft, 20 closed tabs and a combined 4 MB text budget. Older entries are pruned. Recovery is not a backup of every keystroke; keep independent backups of important SQL.

## SQL shortcuts and query queue

Choose **Query shortcuts** above the editor or in **Commands**. Save an abbreviation and SQL template in Query Library. Type the abbreviation, review its completion and press Enter or Tab. Expansion does not run SQL; one Undo reverses it. Shortcuts use saved library SQL, not unsaved draft edits.

Open **More SQL actions → Query queue** to review statements and start them explicitly. Parameters are collected separately for each statement. The queue accepts up to 20 read-only SELECT/WITH statements, with up to 1,000 fetched rows per statement and 10,000 in total. Choose whether to stop after an error. Stop prevents remaining statements from starting; an in-flight request can finish. This is not a transactional database script.

Queue results become saved evidence only when requested. The last completed result also appears in the normal grid. Each ordinary execution supports up to 1 MiB of SQL, 10,000 rows, 512 columns or 500,000 cells; Oracle may allow less. Read-only SQL can still call functions with side effects. Use least-privileged access.

## Typed inputs and presets

Use **Text** for identifiers with leading zeros. Enter values without SQL quotes. Number, Date, Timestamp and NULL remain typed values passed separately from SQL. Definitions can add readable labels, descriptions, required inputs and default types for the exact SQL and connection.

Saving definitions does not save current values. Named presets save values only on an explicit save and load only when requested. Treat them as business data. Values are not written into query history or SQL files; literals already in SQL and values returned in results can still be saved.

**Connections → Check parameters** uses a fixed text-and-number probe without modifying catalog objects. An inconclusive check is not proof that parameters are unsupported. If the report contract needs updating, review **Use separate parameter report** with the report owner. Save & test prepares missing objects under distinct names without overwriting existing models. Tenant permissions and database access still apply.

## Read-only BI Publisher report catalog

Select a saved connection and explicitly browse folders. Filter visible items, inspect a report's model reference, and review SQL datasets and parameter metadata. **Open SQL draft** makes a local copy for review. The catalog browser does not edit, upload, rename, delete or execute original Fusion objects.

A copied query does not reproduce the model's full execution or security context, data links, lists of values, triggers, bursting or multi-dataset behavior. Review its data source and parameters before running it through the selected FUSE connection.

Capture a model, multiple selections or a folder with optional subfolders. Snapshots preserve original export bytes and SHA-256 checksums, record skipped items and explicit limits, avoid identical captures, and compare by full catalog path. Supported XML and ZIP definitions can be inspected offline without contacting Fusion.

These are FUSE snapshots, not Oracle catalog import archives. A capture is sequential, not an atomic backup. It cannot establish visibility of hidden or inaccessible objects. Limits include 100 files, 50 visited folders, 16 MiB of decoded object bytes and a 120-second request budget; inspect completeness and skipped entries before relying on a snapshot.

## Investigations and captured results

Create a local case to record a question, scope, hypotheses, findings and gaps. Starter cases cover missing workers, duplicate report rows, payroll differences, environment drift and delayed approvals. They guide investigation; they do not establish root causes on their own.

Capture results with their SQL, connection label, execution details and fetch limits. Captures contain only fetched rows and are limited to 4 MB. Checks cover unique keys, required values, row counts and numeric totals. Comparisons use business keys, ignored columns, exact decimal tolerance and explicit date/text normalization. Duplicate keys remain visible rather than being paired arbitrarily.

Save case edits explicitly. Local document storage is shared by parameter profiles, catalog snapshots and investigation documents, with up to 100 documents and 128 MB total. Review SQL and captured data before exporting a case or sharing any file. Exports do not automatically redact business data; protect stored files and keep controlled backups.

## Coding tools and typed approval

Use **Settings → Coding tools** for a local MCP-compatible client. Review the exact SQL, typed values and selected connection before approving a run. Approval binds them to one execution; changing any of them requires another review. No connection is chosen automatically by the companion.

Library creation, execution and result sharing are separate permissions, off each session. Runs return status and counts by default. Optional result samples require session permission and consent for that run. They can reach the coding tool's provider without automatic redaction. Samples are limited to 100 rows, 100 columns and 64 KiB, expire after five minutes, and can be cleared or revoked. FUSE cannot recall external copies. The coding tool's independently granted file and command permissions still apply.

## Build checks and remaining validation

The portable was assembled locally on macOS with a pinned official Windows Node runtime. Source checks passed 1,001 JavaScript/TypeScript tests (3 skipped), 141 Rust tests and 11 browser regressions, with focused follow-up checks. Catalog, parameter and snapshot browser checks used synthetic responses. Packaged gateway, MCP and UI checks used host Node.

Those checks do not establish Windows client launch, enterprise-policy behavior or live Oracle tenant support. Those validations remain pending and follow this portable publication. No new EXE, MSI or Store package, signing or certification is claimed.

On an authorised Windows device, check first launch, save and reopen, password retention, workspace recovery, parameter input, report browsing, offline snapshot inspection and coding-client approval. Validate the representative report and permissions with the tenant owner before relying on the workflow. Do not send credentials, tenant addresses, personal data or raw logs with feedback.

FUSE is independent software, with no Oracle affiliation or endorsement. Oracle is a registered trademark of Oracle and/or its affiliates. Read the notices bundled with the download.

Release notes: https://github.com/anandvegaraju/FUSE-Downloads/releases/tag/v1.0.0-rc.29-build.1

Privacy notice: https://www.fusesql.com/privacy