Review Conversion Outputs
Open a conversion from the Converter list to review its status, logs, generated documentation, and target-specific output.
Status and progress
Section titled “Status and progress”Running conversions show the current pipeline step, step count, progress, and streaming logs.
Some Tableau BRD and target BRD sections may become available before the full conversion completes. When sections appear during processing, you can open them from the conversion detail page and start reviewing them while the rest of the job continues.
Completed conversions open to the Report tab. Failed or cancelled conversions open around failure or cancellation context, job information, logs, and resume controls so you can see where processing stopped.
Report
Section titled “Report”The Report tab summarizes a completed conversion and links the generated outputs.
Use it to review:
- Job metadata, including project, target, status, timestamps, and duration.
- Conversion result guidance.
- Downloadable project artifacts.
- Tableau and target BI BRD sections.
- Full Tableau and Power BI BRD downloads when available.
- Processing notes and warnings.
- Fabric deployment options when the output state supports deployment.
Conversion Results
Section titled “Conversion Results”For Power BI output, the Conversion Results section is the first place to review the generated project.
It can include:
- a result banner with next-step guidance
- Download Power BI Project
- data source instructions for Power BI Desktop
- Fabric deployment controls when deployment is available
- Fabric deployment logs after a deployment attempt
Always read the result banner before deploying or sharing the output. It explains whether the project is ready to deploy, needs local refresh, needs file path updates, needs gateway configuration, or completed with issues.
BRD documentation
Section titled “BRD documentation”Converter jobs can generate source and target business requirements documentation.
The Tableau documentation explains the source workbook structure, worksheets, dashboards, filters, calculations, and visual behavior that Antares detected.
The target documentation explains how Antares interpreted that source content for the selected BI platform. Review it before accepting, redesigning, or deploying the converted output.
BRD sections appear as expandable sections on the conversion detail page. When the full BRD is available, use the download link beside the BRD heading.
Power BI outputs
Section titled “Power BI outputs”Power BI conversions can include:
- downloadable Power BI project output
- Power BI semantic model and report artifacts
- Tableau BRD sections
- Power BI BRD sections
- conversion report
- processing logs
- optional cache artifacts
Read the result guidance before deployment. Antares may ask you to update file paths, refresh data in Power BI Desktop, configure a gateway, review .tmdl files, or validate cache behavior.
Power BI result guidance usually falls into one of these states:
| Result state | What it means | What to do next |
|---|---|---|
| Ready to deploy with cache | The output includes a pre-built data cache. | Deploy to Fabric, then validate the report and semantic model. If cache validation fails, download the project, remove the cache file, and refresh in Power BI Desktop. |
| External sources only | The workbook uses external data source connections. | Deploy to Fabric, configure the gateway connection, and verify server names, database references, and connection strings in .tmdl files. |
| Calculated sources with cache | All data sources are calculated and cache output is included. | Deploy to Fabric and validate that the report loads with data. |
| No pre-built cache | The output does not include a data cache. | Download the project, open it in Power BI Desktop, and refresh the semantic model manually. |
| File-based sources without cache | File paths must be made valid for Power BI Desktop. | Update File.Contents(...) paths in .tmdl files, then refresh in Power BI Desktop. |
| Mixed data sources | The workbook uses both file-based and external sources. | Update file paths, refresh locally, deploy to Fabric, and configure the gateway connection. |
| Completed with issues | The semantic model may be incomplete. | Download the project, review generated files and logs, and fix data source connections or model issues manually. |
Fabric deployment
Section titled “Fabric deployment”Fabric deployment is available only for completed Power BI conversions whose output state supports deployment.
When deployment is available, select a Fabric connection, select a workspace, and choose Deploy to Fabric. Deployment can use:
- PBIX import when a data cache is included
- PBIP deployment when the project does not include a cache
After deployment, review Fabric Deployment Logs on the conversion detail page. Successful logs can include semantic model deployment, report deployment, and a workspace link. Partial or failed deployments include warning or error messages.
Databricks AI/BI outputs
Section titled “Databricks AI/BI outputs”Databricks AI/BI conversions focus on target-specific migration guidance rather than Fabric deployment.
Review the generated target documentation for:
- SQL-native fit.
- Tableau interactions that need redesign.
- dashboard rebuild recommendations.
- unsupported or partially supported Tableau behavior.
- source calculations and data patterns that need target validation.
Use this output to plan AI/BI rebuild work and validate whether the workbook is a good candidate for automated or assisted migration.
Logs and Info
Section titled “Logs and Info”Use Logs & Info to inspect job metadata, processing events, warnings, errors, and retry context.
Job information includes:
- status and target
- project and report name
- job ID
- created, started, and completed timestamps
- duration
- error and warning summary when logs are available
Logs are especially useful when a conversion stops before completion, when an output is missing, or when a generated report includes warnings.
Retry and resume
Section titled “Retry and resume”Failed or cancelled conversions can be resumed when Antares has enough job context to continue.
For failed conversions, use Resume from last step for the normal recovery path. Use Resume from step only when you know which pipeline step should be rerun.
For cancelled conversions, use Resume from step to restart from a specific pipeline step.
Previous logs remain available, and new retry logs are appended to the job history.