Manage report and file metadata
Report metadata describes reports, information items, and table associations. File metadata describes objects harvested from storage servers. Their collection and query paths differ.
| Area | Includes | Does not include merely because input is a file |
|---|---|---|
| Reports | Supported BI reports and custom DAM/SQLink imports | Dictionaries, DDL, ordinary server files |
| Files | File server files and folders | Dictionaries, DDL, API metadata, metamodel templates |
Create a report
- Open Reports and select a folder.
- Create a report with basic properties and folder information.
- Add information items and table associations.
- Save and verify properties, folder, and related objects.
Use Report harvesting for supported BI tools rather than manually duplicating their results. Supported and custom reports share this area.
Import reports
- Download the report template.
- Complete properties and relationships.
- Select update or overwrite behavior and upload.
- Verify results, counts, and table associations against the input.
Check matching names and scope before overwrite.
Maintain and export reports
View details, edit properties, or select rows for bulk deletion after reviewing scope. Folder export covers the current folder only. View Basic lineage where parsed relationships exist; text descriptions do not generate lineage.
View and download files
Only File Storage Server harvesting produces these entries. Dictionaries, DDL, APIs, and metamodel files create structured objects in Datasets.
- Search the Files list.
- Open details and maintain editable properties as needed.
- Select files and download.
- Verify contents and follow organizational storage and use rules.
For missing files, check the subtype, task execution, paths, scope, and permissions. Query Datasets for parsed structured inputs.
