Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
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!
Don't use values as column names, Unpivot your data to have a column for "time period" .
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?
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.
Hi lbendlin,
So now I'm not using pivot action, but I'm still getting the "Column wasn't found" error even though I can see them in the preview.
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 'Month-Year' of the table wasn't found. Details: Reason = Expression.Error; Detail = Month-Year; Microsoft.Data.Mashup.Error.Context = User
Here I'm attaching my Power Query, thank you very much!
You will want to unpivot your source tables BEFORE you append them.
Can you post a couple rows from each source table?
My source tables are somewhat messy, but they follow the exact same format. There are more than 10 columns in each source table, including time, budget, revenue, percentage, etc. Shall I clean/transform and unpivot all source tables and then append all together?
I cannot assist you if you are unable to provide sample data. I hope someone else can help you further.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
14 | |
13 | |
12 | |
12 | |
12 |