Report Capabilities & Data Access
Antares reports are capability-based. Analyzer shows the report sections it can support with the workbook, Tableau, and usage data available for a specific analysis.
Capability-based reporting keeps results honest: if Antares cannot access a source, it does not fill dependent sections with empty or misleading data.
Capability matrix
Section titled “Capability matrix”| Capability | Enables | If unavailable |
|---|---|---|
| Workbook upload | Single-workbook structural analysis, field statistics, complexity scoring, and migration blockers. | Use a Tableau connection if you need environment inventory, ownership, users, groups, or usage metrics. |
| Tableau API access | Environment inventory, projects, owners, workbook metadata, and workbook selection. | Environment analysis cannot run, or results are limited to uploaded workbook content. |
| Workbook download access | Workbook structure analysis, field statistics, scoring, blockers, warnings, and workbook detail pages. | Antares may list visible content but cannot fully analyze workbook structure. |
| Users and groups visibility | Ownership, user, and group context in Analyzer reports. | User and group sections are hidden or marked limited. |
| Admin Insights | Tableau Cloud usage events, user activity, and period-based usage reports. | Usage sections are unavailable for Tableau Cloud analyses. |
| Tableau Server Repository | Tableau Server usage statistics and access patterns. | Usage sections are unavailable for Tableau Server analyses. |
| Microsoft Fabric connection | Fabric workspace browsing, Power BI deployment actions, deployment logs, and workspace validation. | Analyzer reports still work, but Converter cannot deploy Power BI output directly to Fabric. |
Why sections may be hidden
Section titled “Why sections may be hidden”If Antares cannot access a data source, related report sections are hidden or marked unavailable.
Common examples:
- Usage charts require Admin Insights for Tableau Cloud or Tableau Server Repository access for Tableau Server.
- User and group context requires the Tableau identity to see users and groups.
- Workbook details and field statistics require workbook upload or workbook download access.
- Fabric deployment actions require a valid Microsoft Fabric connection and workspace access.
For Tableau environment analyses, the connection pre-check shows which capabilities Antares detected before the job starts.
Analysis vs. deployment access
Section titled “Analysis vs. deployment access”Tableau, workbook, user, group, and usage access affect Analyzer reports.
Fabric access affects deployment after conversion. You do not need a Fabric connection to analyze Tableau workbooks, calculate migration scores, or review Analyzer results.
Use Fabric access when you want Converter to deploy completed Power BI output to a Microsoft Fabric workspace.
Recommended access model
Section titled “Recommended access model”Start with the narrowest access that supports your goal.
- For a one-off workbook report, upload a
.twbor.twbxfile. - For migration scoping, connect Tableau API access and allow workbook download.
- For prioritization, add Admin Insights or Server Repository usage access.
- For deployment, add Microsoft Fabric access after Power BI conversion output is ready.
Where to configure or troubleshoot access
Section titled “Where to configure or troubleshoot access”- Use Connect Tableau for first-time Tableau connection setup.
- Use Tableau Connections for detailed authentication, permissions, usage data, and pre-check behavior.
- Use Create an Analysis to understand the Analyzer pre-check.
- Use Common Issues when usage sections are missing.
- Use Fabric Connections when you need Power BI deployment to Microsoft Fabric.