Forum Discussion
Power BI Service Refresh Error: "We cannot convert the value '[Table]' to type Table", Desktop works
Hi everyone,
I'm running into a Power BI Service refresh issue that I can't seem to solve.
The Error
The dataset refreshes successfully in Power BI Desktop, but fails in Power BI Service with:
Expression.Error: We cannot convert the value "[Table]" to type Table.
Details:
Reason = Expression.Error
ErrorCode = 10277
Value = [Table]
The frustrating part is that Desktop works perfectly, so this appears to be a Service-only evaluation issue.
My Query Structure
I have a query that:
- Loads a custom data collection table.
- Filters active parameters.
- Joins to a parameter mapping table.
- Groups source records by parameter value.
- Uses a custom function (fnExpandMappedParameter) to dynamically expand parameter data.
- Combines all returned tables into a single table.
A simplified version:
Source = base_table_custom_data_collection, FilteredParams = JoinMapping = GroupedSource = Joined = AddTables = Combined = |
What I've Already Tried
1. Table.Buffer()
I buffered both source and parameter tables, no change.
2. Verify Nested Tables
I checked the columns involved, both appear as nested tables in Desktop. No obvious issues appeared in preview.
3. Expand Mapping Earlier
I tried expanding the Mapping column, however, downstream logic expects: mapping = [Mapping], which no longer exists after expansion. This didn't solve the refresh issue and likely breaks the original function design.
4. Considered Moving Logic to SQL
I considered moving the transformation to SQL Views or Stored Procedures. However, the solution depends on multiple parameter tables, dynamic mappings, custom functions and dynamic column generation. So it doesn't feel like a practical SQL rewrite without substantial redevelopment.
I'm wondering if Power BI Service is evaluating one of the nested table objects differently than Desktop. Perhaps somewhere a nested table is being interpreted as the text "[Table]" rather than an actual table object.
The part I'm most suspicious of is the below, since this is where nested tables are being passed into a custom function:
fnExpandMappedParameter(
tbl{0}[Data],
param,
mapping
)
Has anyone encountered a Desktop vs Service issue where a nested table becomes the text value "[Table]" during refresh? Is there a better architectural approach for handling dynamic parameter expansion like this that avoids nested table evaluation issues?
Are there known limitations with some of the syntaxes used, that behave differently between Desktop and Service?
Any suggestions would be greatly appreciated. I've spent quite a bit of time troubleshooting this and have reached the point where Desktop works consistently but Service continues to fail with the same error.
Thanks!
Its usually happens due to Privacy level of your data source, update the web privacy level same as your desktop file and you should be good
6 Replies
- arvindsingh802Community Champion
Its usually happens due to Privacy level of your data source, update the web privacy level same as your desktop file and you should be good
- krishnakanth240Super User
Hi aidelasks
Ensure to match privacy levels for data source in Power BI Service dataset settings (Settings - Datasets - Data source credentials - Privacy level) since Desktop and Service can evaluate nested table firewall rules differently