Problem Statement:
Currently, HCL Domino supports modifying database designs via JSON (e.g., through the Domino REST API or Domino Designer JSON features). However, this functionality is largely unidirectional or template-based.
There is no native way to export the design of an existing, live database (NSF) into a JSON format.
The Current Workflow Gap:
DXL is too complex: To export an existing database design for external modification, we must use DXL (XML-based). DXL is verbose, difficult to read, hard to edit manually, and fragile when modified outside of Domino.
Domino Restyler is limited: Restyler only handles visual themes/styles (CSS/UI), not the logical structure, fields, views, or agents.
JSON Import works, but Export does not: While we can import JSON to create or modify designs, we cannot "snapshot" the current state of a specific existing database into a clean, editable JSON file.
Why this matters:
Developers and Admins often need to:
Extract the design of a specific production/testing database to modify it externally (e.g., in a code editor with Git versioning).
Compare designs between two databases using standard JSON diff tools.
Automate design updates via CI/CD pipelines by exporting current state → modifying JSON → importing back.
Proposed Solution:
Implement a feature in Domino Designer or the Domino HTTP API that allows users to:
Select an existing NSF database.
Export its entire design (or selected design elements) into a structured, human-readable JSON file.
-
This JSON file should be compatible with the existing JSON import functionality, enabling a full round-trip workflow:
Key Benefits:
Modern Development Workflow: JSON is the standard for configuration and design in modern software development. It integrates seamlessly with Git, CI/CD, and code editors.
Reduced Complexity: Replaces the need for complex DXL manipulation for many common use cases.
Precision & Control: Allows developers to see exactly what is in the database design in a clear format, making audits and migrations easier.
Complements Existing Features: Leverages the existing JSON import engine by adding the missing "Export" leg to the workflow.
Great idea!
The disadvantage of DXL is that it requires a rigid sequence of tags, which is long outdated. It is also difficult to read and redundant in size.
If you implement such JSON functionality, then in the future we can completely avoid such an inconvenient format as DXL.
Many HCL Domino databases have evolved historically over time. When customers introduce a new corporate design, it is currently almost impossible to implement the same design consistently across different databases within a short period of time.
We need the described functionality to efficiently apply a consistent corporate design across all Domino applications and other databases without having to modify each application individually.
Moving to the Domino Designer category