01 / REPORTS AND DATA
Choose the format for the purpose
Exports can cover a client, location or rack; topology uses the active filters. PDF supports readable handover documentation, JSON structured data and CSV tabular work with devices, connections or history.
Reports can combine maps, rack views and tables. Options include page size and orientation, theme, cable labels, line appearance, selected fields and optional photographs. Selecting report fields is separate from the full JSON variant intended for import.
02 / REPORTS AND DATA
Reuse settings for later reports
A private export profile stores appearance and information scope. Prepare a technical version for analysis or a simpler handover for documentation readers. Profiles belong to the user account.
History has its own export, with a compact change list or before-and-after values. Reports cover active filter results rather than only the visible list page. For large scopes, consider PDF generation limits and use CSV when more appropriate.
03 / REPORTS AND DATA
Preview first, then import deliberately
Import accepts a RackDocs JSON export. Choose a destination location or code matching, how mounting should be retained and whether new cables may connect compatible existing ports.
The preview lets you inspect duplicates, conflicts and scope before approving selected items. Existing devices, ports and cables are not overwritten. Import covers devices with their ports and selected connections, allowing a controlled addition to existing documentation.
04 / REPORTS AND DATA
Keep reports separate from recovery backups
A documentation export selects information for a particular purpose. It is not a complete image of accounts, permissions, files, history and environment configuration. Import does not restore map positions or manually drawn routes either.
Plan backups separately for the deployment model. A database dump does not automatically include all private attachments. A recovery procedure should cover database, files and configuration and be verified by the administrator.
Practical workflow
Prepare a location handover
- Set the location, statuses and other relevant filters.
- Choose sections, fields, map appearance and optional photos, then save a profile.
- Generate the right format, using full JSON for data intended for re-import.
Import accepts RackDocs JSON files up to 10 MB and does not replace full installation recovery. Photos are not embedded in JSON. Export scopes and limits need to be considered for large environments.
Screenshots come from the working RackDocs application and show a demonstration environment with fictional infrastructure. They include selected views and screen details; the application is evolving. Screenshots retain the Polish interface in this English guide.