Exporting Report Metadata (Categories, Assignments)

When exporting reports, either via the UI or the API, you must explicitly set the corresponding flags for inclusion . Using the API function `XXEN_API.EXPORT_FILE_DATA`, you set `p_type` to ‘Reports’ and use the parameters `p_include_lovs`, `p_include_categories`, and `p_include_assignments` with a value of ‘Y’ , , . This ensures that all related metadata required for seamless deployment is packaged within the XML output .

You should use the ‘Columns’ option (or `p_include_columns` parameter) only if you specifically have multi-language column translations or column-specific number format settings that need to be migrated . If you have a large number of reports, enabling this option can significantly slow down the export process because the database must parse all exported report SQLs to identify the included column names . If you only rely on site-level number formatting, exclude this option.

Yes, during the import process (XML Upload), reports are automatically assigned to categories . This automated category assignment relies on the originating concurrent program’s application module, which is mapped in the lookup `XXEN_REPORT_APPLICATIONS` . For example, reports originating from the AP application module would be assigned to the corresponding AP category defined in that lookup .

If an imported parameter references a shared LOV that does not yet exist in the destination environment, Blitz Report loads that parameter but configures it using a custom LOV instead of the missing shared LOV . This allows the report to function, but you would ideally import the shared LOV definition first to ensure it remains centrally managed .