ZuloOne Studio

Visual Studio Code extension for the ZuloOne business layer. It follows the Dynamics 365 Finance and Operations development tools: an Application Explorer over the models, and an element designer with a design tree and a property grid.

The files stay the workspace JSON. Saving a property writes that file; the running stand picks it up through the usual workspace sync. Unknown keys are left in place. An existing metaId is never regenerated.

First slice

• Application Explorer. By model (the default): a model, then object types inside it. By object type: Dictionaries, Documents, and the rest across models, with the model name on each row. The view title switches the grouping and can narrow to one model.
• Designer for dictionaries, documents, table parts, extended data types, enums, number sequences, registers, and extension aggregates.
• Scripts. Event handlers, transaction scripts, services, and commands open as the sibling .cs file. A dictionary, document, or table part can grow an owner event handler. A document can grow a transaction script linked to a subtype. Extend creates the aggregate and a chain handler in a higher-layer model.
• Registers. New Register creates the element with dimensions, resources, and analytics. Each of those can be added and deleted in the designer. An analytic is picked from the Analytics folder.
• New dictionary and new document, from the group node in the explorer.
• New field, new subtype, and adding an existing table part to a document.
• Open on a reference property jumps to that element (the EDT of a field, the table part of a document).

Creating an element in Core is not offered. Delete Element removes the file (and a sibling .cs if present). The database object stays until Publish to Environment.

Live sync mode is ↔ (both), ↓ (environment wins), or ↑ (disk wins). Models the signed-in user cannot write always pull. Publish pushes writable files and prunes ledger-gone objects. Mirror selected models keeps a partial tree (Core is always included). Open editors take a 45-second file lease so another developer cannot push the same path.

A VSIX is built on tag studio-N and attached to the GitHub Release. The same workflow publishes to the Visual Studio Marketplace when the repo secret VSCE_PAT is set (Azure DevOps PAT with Marketplace Publish, publisher zuloone). Search ZuloOne Studio in Extensions, or Developer → Workspace sync (Install Studio) for a sideload.

Run

Open this folder in VS Code or Cursor and press F5. The Extension Development Host opens the business-layer workspace. The ZuloOne icon on the activity bar is the Application Explorer.

A double-click opens the designer. Open JSON in the designer toolbar returns to the text editor.

Connect to Environment asks for the stand address and a user with the Developer permission. The extension downloads that stand's workspace mirror, unpacks it, and starts it against the open folder. The password stays in the editor's secret storage. The mirror is a user process, not a Windows service: a push is logged with the person who signed in. The status bar shows the stand while sync is running.