TDS Endpoint - Missing Tables

(4) Share

Report

Posted on by VS-06031258-0

Hi Team,

We are currently having a Power BI report which connects to Dataverse via OData connector. There is a plan to use to the TDS endpoint instead for faster data refreshes.

For most tables we have written SQL queries in SSMS to return the same data. But for teamtemplate table, We are getting an error like this :

{"Message":"Table teamtemplate is not available for reports. Line:4, Position:6"}

Has anybody ever encountered this issue and/or know a solution? Thank you.

Categories:

Dynamics 365 general

I have the same question (0)

All responses (4)

Answers (1)

Vahid Ghafarpour 11,930 Super User 2025 Season 2 on at

Like (0)

Report

TDS Endpoint - Missing Tables

If any of the responses helped resolve your issue, please take a moment to mark the best answer. This helps others in the community quickly find solutions to similar problems.

To do this, simply click the "Does this answer your question?" button on the most helpful response and like the helpful posts. If your issue is still unresolved, feel free to provide more details so the community can assist further!

Thanks for being an active part of the Dynamics 365 Community!

Was this reply helpful? Yes No
Suggested answer

Jonas "Jones" Melgaard 4,872 Super User 2025 Season 2 on at

Like (2)

Report

TDS Endpoint - Missing Tables

The reason is that's it's not a "real" table as such that's backed by the Dataverse database, but it's based on the metadata that's availabe in the Power Platform solutions.
So the SQL interface don't know how to handle them

There is an article about it here: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/table-solution-objects

You also get a warning when you browse the tables in the maker portal:

Was this reply helpful? Yes No
Verified answer

Daivat Vartak (v-9d... 7,829 Super User 2025 Season 2 on at

Like (2)

Report
TDS Endpoint - Missing Tables

Hello VS-06031258-0,

You've encountered a known limitation when trying to access the teamtemplate table (specifically, the Team Template entity) through the Tabular Data Stream (TDS) endpoint in Dataverse for Power BI. This entity is not directly exposed for reporting purposes via TDS.

Here's a breakdown of why and what you can do:

Understanding the Limitation:

TDS Endpoint Restrictions: The TDS endpoint in Dataverse is designed for reporting and analytics, and it doesn't expose all Dataverse tables. Some system tables, configuration tables, and internal tables are deliberately excluded.

teamtemplate Entity: The teamtemplate entity falls into this category. It's primarily used for internal system configuration and isn't intended for direct reporting.

Security and Performance: Exposing all tables through TDS could pose security risks or impact performance.

Solutions and Workarounds:

Alternative Data Retrieval (Not Ideal):

OData (Continue Using): If you absolutely need to access the teamtemplate data, you'll likely have to continue using the OData connector for this specific table. This negates the benefits of switching to TDS for faster refreshes.

Limitations: Slower refresh times compared to TDS.

Custom Entity (Recommended, but Requires Development):

Create a Custom Entity: Create a new custom entity in Dataverse that mirrors the relevant data from the teamtemplate entity.

Populate the Custom Entity: Use a Power Automate flow, a plugin, or other methods to populate the custom entity with the necessary data from teamtemplate.

Use TDS with Custom Entity: Access the custom entity through the TDS endpoint in Power BI.

Advantages: You can control which data is exposed and optimize it for reporting.

Disadvantages: Requires development effort.

Dataverse Web API (Potentially More Complex):

Use the Web API: You could potentially use the Dataverse Web API to retrieve the teamtemplate data and then push it into Power BI.

Complexity: This approach is more complex than using the TDS endpoint and requires more development skills.

Performance: Performance might not be as good as TDS.

Evaluate the Requirement:

Business Need: Carefully consider whether you truly need to report on the teamtemplate data.

Alternative Approaches: Explore if there are alternative ways to achieve your reporting goals without directly accessing this table.

Recommendation:

The recommended approach is to create a custom entity that mirrors the relevant data from teamtemplate. This gives you the most control over the data and allows you to use the TDS endpoint for faster refreshes.

Steps for the Custom Entity Approach:

Create a Custom Entity: Create a new custom entity in Dataverse.

Define Fields: Add the necessary fields to the custom entity to match the data you need from teamtemplate.

Create a Power Automate Flow (or Plugin):

Create a Power Automate flow that triggers when a team template is created or updated.

Retrieve the relevant data from the teamtemplate entity.

Create or update a record in your custom entity with the retrieved data.

Connect to TDS: Connect Power BI to the TDS endpoint and use the custom entity for your reports.

By implementing this approach, you can overcome the limitation of the TDS endpoint and achieve faster data refreshes for your Power BI reports.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Holly Huffman 6,520 Super User 2025 Season 2 on at

Like (0)

Report
TDS Endpoint - Missing Tables

Hi there! Good morning, evening, or afternoon - depending on where you are :) Hope you are well today! I see you posted this a while ago - hoping you have resolved by now but incase not, here are a few thoughts:

The error message "Table teamtemplate is not available for reports" indicates that the teamtemplate table is not exposed through the TDS (Tabular Data Stream) endpoint. This is a common limitation, as not all Dataverse tables are available for querying via TDS. Here are some steps and workarounds to address this:

1. Verify Table Availability in TDS Endpoint

The TDS endpoint only supports tables that are enabled for reporting.

To check if the teamtemplate table is enabled:

Navigate to Power Platform Admin Center > Dataverse > Tables.

Open the teamtemplate table and ensure the Enable for Reporting option is turned on.

2. Use OData Connector for Missing Tables

If the table is not available via TDS, you can continue using the OData connector for this specific table while using TDS for others.

Combine the data from both sources in Power BI to create a unified report.

3. Refresh TDS Metadata

If the table was recently enabled for reporting but is still not accessible, refresh the TDS metadata:

Disable and re-enable the TDS endpoint in the Power Platform Admin Center.

This forces a metadata refresh and may resolve the issue.

4. Create a Custom Table or View

If the teamtemplate table cannot be enabled for reporting, consider creating a custom table or view in Dataverse:

Use Power Automate or a plugin to copy the data from teamtemplate to a custom table that is enabled for reporting.

Query the custom table via the TDS endpoint.

Hope this helps some!

Was this reply helpful? Yes No