Data Exchange & Integrations
This page is a short map for integration and data exchange topics in HDC. Use it to choose the right sub-page depending on whether you need to import data, export packages, map identifiers, embed the viewer, call APIs, or synchronize metadata with external systems.
Start here
Need | Go to | What you will find |
|---|---|---|
Bring data into HDC | Import packages, supported package types, matching rules, import options, logs, reports, and troubleshooting unmatched objects. | |
Take data out of HDC | Exporting objects, documents, geometry, attachments, FI2 or HDC internal packages, and downloading export results. | |
Understand exported geometry | Package structure, XML files, SVG geometry, spots, redlining, units, and transformations. | |
Map external systems to HDC | External domains, object and field mappings, identity rules, layer mappings, and import/export of domain configuration. | |
Check internal HDC classes and fields | The internal class and field catalogue used as the HDC side of mapping in TDXM. | |
Embed HDC Viewer in another application | Embedded viewer startup parameters, JavaScript API calls, iframe setup, postMessage communication, and viewer events. | |
Build REST/API-based integrations | Explore Documents and Spots with API and MasterGUID / FMGUID | Example API flows for documents, spots, perspectives, default documents, and object lookup by GUID. |
Automate large imports | A desktop helper for uploading large packages, running imports, and monitoring background processing. | |
Synchronize with Asset+ | Two-way metadata synchronization, live Asset+ data view, sync statuses, conflict merge process, configuration, and authentication. | |
Configure identi365ty/authentication dependencies | Security note for users authenticated through LDAP/ADFS and role assignment implications. |
Data exchange building blocks
Import is used when external packages should create or update HDC objects, documents, drawings, metadata, layers, and links. Matching depends on configured identifiers, GUID rules, search fields, and the selected External Information Domain.
Export creates a package from selected HDC data. Depending on options, the package can include object structure, metadata, documents, drawings, geometries, and attachments. HDC internal export is also the basis for moving data between HDC databases.
Information Domains define how HDC understands another system. Internal domains describe HDC classes and fields; external domains describe external class names, fields, identifiers, and layer mappings. They are the key configuration layer for both import and export.
APIs and embedded integrations
For interactive viewer integrations, start with the Embedded Viewer API. It explains how to open HDC in embedded mode, show objects by internal IDs, external domain IDs, or MasterGUID, control 2D/3D/point cloud preferences, and read selected objects from the viewer.
For website integrations, use the 3rd party website integration page together with the Embedded Viewer API. It explains iframe setup, anonymous or authenticated loading, URL parameters, Window.postMessage communication, and available events.
For REST-style data access, use the API use case page and the MasterGUID / FMGUID page. These explain how to discover linked documents, content containing spots for an object, default documents, metadata by GUID, and other GUID-based object operations.
Synchronization and automation
HDC Remote Agent helps integrators upload and import large packages without implementing the full API flow. It supports chunked upload and background processing.
Asset+ Sync supports two-way metadata synchronization with Asset+, including automatic and manual sync, conflict handling, live data view, and configuration of mapped fields. It uses MasterGUID/FMGUID as the main cross-system identifier.
Identity, access, and identifiers
MasterGUID / FMGUID is the preferred stable identifier for objects across integrated systems. Use it when possible to simplify API calls and avoid translating between internal HDC object IDs and external IDs.
LDAP is relevant when integrations rely on external authentication. Pay attention to role assignment, because mapping broad external groups to HDC roles can grant system access to all authenticated users.