Forum Discussion
Error: column wasn't found
Hi everyone,
I'm encountering an issue while refreshing my dataflow, specifically during the "WriteToDataDestination" activity. In my query, I combined several tables using the "Append Queries as New" function. After that, I performed various transformation actions such as adding columns, removing columns, pivoting, etc.
The resulting view has several columns. The first column is a completely new column named "line" which contains two new text values. The remaining columns have new names such as "Jan-2024", "Feb-2024", "Jan-2025", etc., and their values are derived from the combined tables.
I was able to successfully publish the dataflow, but I encountered the following error when attempting to refresh it:
Append_WriteToDataDestination: Mashup Exception Expression Error Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: Expression.Error: The column 'Jan-2024' of the table wasn't found. Details: Reason = Expression.Error;Detail = Jan-2024;Microsoft.Data.Mashup.Error.Context = User
Any help or insights to resolve this issue would be greatly appreciated. Thank you!
7 Replies
- lbendlinSuper User
Don't use values as column names, Unpivot your data to have a column for "time period" .
- Jie09Frequent Visitor
Hi lbendlin, thank you for your help! Could you please elaborate on why I should restructure my data to have time periods as values in a single column instead of making them columns themselves? Currently, I am using a pivot operation to create columns like "Jan-2024", "Feb-2024", "Jan-2025", etc., because this format aligns with what my colleagues use for their analysis. Are you suggesting that having time periods as column names could be causing this error?
- lbendlinSuper User
Yes, that is what I am suggesting. It is a typical pattern in Excel, but Power BI is not Excel. Power BI wants fixed column names and narrow tables. Let the visuals do the pivoting for you.