ERP Export
Use ERP Export to send WSi project data to your ERP system. There are two ways to export:
- JSON → Server sends data directly to your ERP over HTTP — no manual file handling. WSi authenticates with the server and sends a JSON payload.
- JSON → File saves the same JSON to a file on your machine or network drive.
Both modes use the same JSON structure and interface configuration (tsGraphRep or BOM). The choice is only a matter of how the data is delivered.
When to Use ERP Export
Choose ERP Export when:
- Your organisation has a server endpoint configured for receiving WSi data
- You want to push export data automatically without saving a file first
- You need to integrate with a custom ERP system
INFO
For IT-Blech or Oseon ERP systems, WSi has dedicated export formats:
- IT-Blech Export — XML format, enabled when IT-Blech module is licensed
- Oseon Export — native Oseon format, enabled when Oseon module is licensed
For saving a file to your machine or network drive, see Local Export instead.
JSON → server
- Click File → Export → ERP Export (JSON → Server), or use the toolbar button.
- WSi checks that all parts are export-ready. If there are errors, a dialog lists them — fix them first, then try again.
- If no URL is configured, enter your ERP server endpoint in the field provided. WSi remembers the last URL you used.
- If prompted, enter your authentication credentials (basic auth or bearer token). WSi stores them for future exports.
- WSi sends the JSON to your server. A confirmation appears when the transfer succeeds.
For the interface type and resource options, see Standard Interface.
WARNING
Exports are blocked if any parts use unlicensed features (welding, machining, coating, punching). Contact your sales representative at WSoptics to activate those features.
TIP
If your server uses a self-signed certificate, WSi asks whether to trust it the first time you connect.
For a step-by-step ERP export setup guide, see JSON → Server above.
What is sent
The JSON payload contains your project data — either a graph representation (full project structure with geometry, articles, and embedded CAD files as base64) or a BOM (bill of materials with components, work steps, costs, and dimensions). Which format is used depends on your interface configuration.
JSON → file
Save the ERP JSON payload to a file instead of sending it to a server:
- Click File → Export → ERP Export (JSON → File), or press Ctrl+J.
- WSi checks that all parts are export-ready. Fix any errors first.
- Choose a location and filename. The default suggested name is
<project_name>.json. - Click Save.
The saved JSON is identical to what would be sent to the server. You can open it in any text editor or load it into another system. WSi remembers the last export directory.
Authentication
WSi supports two authentication methods:
- Basic auth — username and password
- Bearer token — a token string
Credentials are stored securely and reused for subsequent exports.
Configuration
ERP server URL, authentication, and SSL options are stored in WSi's local settings. Your administrator can pre-configure these so you don't need to enter them manually each time.
ERP Integration Settings
Access via Settings → Client → Local ERP settings → Configuration ERP integration.
| Setting | What it does |
|---|---|
| Endpoint URL | The server address WSi sends data to. Accepts http://, https://, and file:// schemes. |
| Quit on successful export | When enabled, WSi closes automatically after a successful export — useful for automated pipelines. |
| ERP Integration Input | Custom key–value pairs merged into the projectUserData field of every export. Allows injecting per-company metadata into the JSON payload. |
| HTTP Request Headers | Additional headers sent with every request (e.g. X-API-Key, X-Company-ID). Each header has a name and a value. |
The endpoint URL, quit-on-success flag, and integration input can each be set to default (pre-configured by your administrator) or custom (overridden per-session in the dialog).
Standard interface configuration
Access it via Settings → Database. Select Advanced Settings from the table list, then open the ERP Interface - Content tab — see Advanced Settings for more on the Database dialog.
Choose which interface type and version WSi uses when generating the export JSON:
Interface Types
| Type | Description |
|---|---|
| tsGraphRep (Graph Representation) | The full project graph — includes all geometry, articles, embedded CAD files as base64, and the complete node structure. Used for backups, sharing, or system integration. |
| BOM (Bill of Materials) | A focused parts list — components with quantities, costs, dimensions, and work step summaries. Used for procurement and quoting. |
Resource and Attachment Types (tsGraphRep)
When the interface type is tsGraphRep, select which resources to include in the export:
| Resource | Format | Description |
|---|---|---|
| Bend drawing | HTML | Bend instructions per part |
| Job card | HTML | Manufacturing job summary |
| DXF | 2D CAD | Cutting contours |
| DXF compressed | .dxf.gz | Compressed DXF |
| GEO | 2D geometry | Gmsh geometry |
| GEO compressed | .geo.gz | Compressed GEO |
| SVG | 2D vector | Scalable vector graphic |
| SVG compressed | .svg.gz | Compressed SVG |
| STEP input | 3D CAD | Loaded assembly geometry |
| STEP input compressed | .stp.gz | Compressed STEP input |
| STEP generated | 3D CAD | Generated/output geometry |
| STEP generated compressed | .stp.gz | Compressed STEP generated |
| PNG images | raster | Screenshots of assemblies |
| Graph components | .wsi | Sub-graphs as separate WSi files |
| Attachments | various | User-defined file attachments |
Export Flags (BOM)
When the interface type is BOM, select which supplementary files to bundle:
| Flag | Description |
|---|---|
| Bend drawing | Include HTML bend drawings |
| DXF | Include 2D cutting contours |
| GEO | Include 2D geometry |
| Job card | Include HTML job cards |
| PNG (input assembly) | Screenshot of loaded assembly |
| PNG (generated assembly) | Screenshot of generated/output assembly |
| STEP (input assembly) | 3D STEP of loaded assembly |
| STEP (generated assembly) | 3D STEP of generated/output assembly |
| SVG | 2D vector output |
| Graph components | Sub-graphs as .wsi files |
| Attachments | User-defined file attachments |
| GLTF (input assembly) | GLTF of loaded assembly |
| GLTF (generated assembly) | GLTF of generated/output assembly |
Versions
Each interface type has a version selector:
- tsGraphRep: v0 (legacy, deprecated) or v1 (current default)
- BOM: v0 (current default)
SSL and Certificates
If your ERP server uses HTTPS with a self-signed certificate, WSi prompts you to trust it on first connection. Trusted certificates are stored locally.
If you encounter SSL errors that block the connection, your administrator can configure WSi to ignore specific SSL error codes (not recommended for production).
See Also
- BOM Export — Bill of Materials format details
- Local Export — Saving exports to file instead of a server
- BOM CSV Settings — Configuring BOM CSV column export
- Project Export Settings — Configuring default file export options