This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
After trying all the suggestions I could find in the forum I'm still getting this error.
There was an error with your subscription "Merchandising" but we still delivered itYou are receiving this email because there was an error with a subscription to Power BI Report "Sample Merchandising Promise Date Changes" created by you.
EmailSubscriptionScreenshotVisualErrorVisual errors were encountered while rendering the artifact. This subscription was delivered to recipients, however one or more visuals may be missing.Fields that need to be fixed : Something's wrong with one or more fields: (Work Orders) COMMENT_DATE, (Work Orders) COMMENT, (Work Orders) USER_NAME, (Work Orders) COMMENT
You can check the latest state of the report by clicking in the button below.
The fields in question (Work Orders) COMMENT_DATE, (Work Orders) COMMENT, (Work Orders) USER_NAME, (Work Orders) COMMENT, in the very early stages of the build were all put in one SQL for a massive 'Work Orders' Table. I wasn't able to use things this way, so I went back to SQL, and split up the tables, creating one 'Work Orders' table, and one 'Comments' table. I didn't over write the Work Orders table, but deleted it from the model, and then re imported giving the new table the same name 'Work Orders' and an all new "Comments" table. I did have one visual that used the (Work Orders) COMMENT_DATE, (Work Orders) COMMENT, (Work Orders) USER_NAME, (Work Orders) COMMENT fields, but I deleted it, and started over. I completed and published my report yesterday, and this message started immediately after creating subscriptions to the report.
I have:
checked that there are no hidden visuals.
checked that there are no measures that included those field names. (actually have no measures at all.)
checked that any splits/merges/new columns didn't include those field names
Deleted the Data Set from the environment, and re published.
I'm still getting the same error message.
Any Idea's?
Solved! Go to Solution.
Hi, @E_Dahlstrom
Have you changed the field names or table names in your power bi desktop file, which may have caused the underlying data set to change.
The error message concerns a column named Merchandising, which is not in your data model. To resolve this issue, you should delete your service dataset and then republish your pbix file.
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I'm going to Click on Accept as a solution because yes, there was a visual hidden that contained fields from the "Massive Work Orders Table" that I mentioned...
I apparently started a visual using the original work order table. When I re created a few tables that would join together instead, I probably minimized the original visual, thinking that if my changes didn't work, I could just bring it back up and continue the work. Well, of course as we all know to be true, I got busy doing something else, and when I came back to my report, I completely forgot about that little grey box in the bottom right...
I've deleted the box, Deleted and republished the Dataset.
problem Solved. Thank you v-zhangti.
Hi, @E_Dahlstrom
Have you changed the field names or table names in your power bi desktop file, which may have caused the underlying data set to change.
The error message concerns a column named Merchandising, which is not in your data model. To resolve this issue, you should delete your service dataset and then republish your pbix file.
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 33 | |
| 25 | |
| 23 | |
| 20 | |
| 15 |
| User | Count |
|---|---|
| 64 | |
| 41 | |
| 27 | |
| 22 | |
| 22 |