Import / Export `.masterlib` Files
Share your master library between TX1 installations using .masterlib (SQLite) or .json files.
Exporting the Library
- Admin → Master Library → Export.
- Choose a format:
- .masterlib (SQLite) — binary, compact, retains exact structure.
- .json — human-readable, good for review and diff.
- Choose options (below).
- Save the file.
Export Options
| Option | Effect |
|---|---|
| IncludeResources | Master resources. |
| IncludeTemplates | Master templates. |
| IncludeFolders | Resource folders. |
| IncludeTags | Tags and mappings. |
| ScopeFilter | Global only, Organisation only, or both. |
| TypeFilter | Limit to specific resource types. |
| Format | Sqlite or Json. |
Importing a Library
- Admin → Master Library → Import.
- Select the
.masterlibor.jsonfile. - Validate — TX1 checks the schema and checksum.
- Preview — shows what will be created / updated / skipped.
- Apply.
Import Options
| Option | Effect |
|---|---|
| ConflictResolution | Skip / Overwrite / Rename / Fail. |
| TargetScope | Import as Organisation or Global. |
| ImportResources / Templates / Folders / Tags | Per-asset toggles. |
Preview First
PreviewLibraryFileAsync(path, options) returns a preview without changing anything. Use it to audit an import before running it.
Schema Version
Each file carries a SchemaVersion. TX1 refuses imports from future versions (forward-incompatible) and upgrades older versions on-the-fly (backward-compatible).
Checksum
Files include a checksum. Tampered or corrupt files are rejected at validation.
Selective Export
ExportSelectionAsync — export only the resources / templates you select (e.g. a specific trade package to share with a partner).
Project-Level Import
ImportToProjectAsync imports library content as project resources, not master resources. Useful when you want to use a master library's content in a one-off project without polluting the organisation library.
Portability Between Organisations
.masterlib files are fully portable. Scenario: parent company ships a library to a subsidiary. The subsidiary imports, gets the same rate cards and templates, and their projects can link back to the imported masters.
Keeping Libraries in Sync Across Sites
Without a shared database, TX1 can't auto-sync libraries. Workflow:
- Parent admin exports weekly to a shared drive.
- Subsidiary admin runs Import, chooses Overwrite conflict resolution.
- Each project's linked resources pick up changes via normal sync.