Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
I have been having issues with this one particular report. Here is the full error message:
Last refresh failed: Wed Dec 27 2017 06:37:50 GMT-0500 (Eastern Standard Time)
Cannot connect to the mashup data source. See error details for more information.Hide details
Underlying error code: | -2147467259 Table: Data Domestic. |
Underlying error message: | The column 'Sales Document Other Field' of the table wasn't found. |
DM_ErrorDetailNameCode_UnderlyingHResult: | -2147467259 |
Microsoft.Data.Mashup.ValueError.Reason: | Expression.Error |
Cluster URI: | WABI-US-EAST2-redirect.analysis.windows.net |
Activity ID: | e0259004-7b20-4d15-849d-0e658eb448f5 |
Request ID: | 59af910c-804d-4c49-986e-699f0c32a542 |
Time: | 2017-12-27 11:37:50Z |
Here is the setup:
Report Structure:
I do know that the PowerPivot Workbook had field name changes (it was a prebuilt workbook built by QQube for simpler reporting).
When I manually refresh the workbook - for a short period, I see the original field names. Once it's done it resumes the changed names. 'Sales Document Other Field'. The original field name is 'SalesTxn Document Other Field'. Several other fields have that 'Txn' added to them originally in the database.
So I know WHAT is causing the error -but I don't know WHY or HOW to get it to stop. If I manually refresh the workbook, and then Power BI file and THEN publish to the Service - everything works fine. No issues whatsoever. It's trying to automatically schedule the refresh from the service when the error occurs.
ANY ideas or assistance with this one would be greatly appreciated.
Hi @heathernicole,
Although we configure scheduled refresh for dataset, the mashup cannot gain the new column name as it has initialize the original column names in Power Query and can only update data for these original columns. That is why it prompts "The column 'Sales Document Other Field' of the table wasn't found." after chaning column name in data resource.
To make the scheduled refresh go on, you have to update the Power Query. You can refresh the dataset manually in desktop, you would get an error like below, please remove the "Changed type" under "Applied Steps", the error will be removed. Then, you need to re-publish the modified .pbix file to service.
Best regards,
Yuliana Gu
@v-yulgu-msft - Thanks for the response! 🙂
I'm already manually refreshing the powerpivot file - and then refreshing the Power BI file and THEN pushing to the service.
But that really isn't a practical setup. If the field names have been changed in the PowerPivot workbook and were pulled into Power BI like - it doesn't make sense that Power BI would still be searching for the original file names.
Maybe I'm not understanding what it's doing in the background - but if the field names change - it would make sense for that to carry over. It just doesn't make sense.
Hi @heathernicole,
I agree with you that the field name should be covered once it is changed in source data. You could submit this feature request at ideas page. Thanks for your feedback. You could paste the link back and I can vote it up for you.
Regards,
Yuliana Gu
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
37 | |
30 | |
18 | |
14 | |
8 |
User | Count |
---|---|
50 | |
38 | |
31 | |
15 | |
13 |