Forum Discussion
Azure Consumption Insights - Column 'Billing Month' in Table 'Summaries' contains a duplicate value
Out of the box, i added the Azure Consumption Insights app, and immediately get this error. The API key etc appear to be correct --- the problem is with the underlying data. I even specified a shorter time frame, so it wouldn't go back to 2017-06 .. but it doesn't seem to honor that part of the config. Any assistance would be much appreciated.
An error occurred while processing the data in the dataset.
Refresh failed: Microsoft Azure Consumption Insights has failed to refresh.
Failure details: Column 'BillingMonth' in Table 'Summaries' contains a duplicate value '2017-06' and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table. Table: Summaries.
Technical Information
Activity Id: 0e62273f-18f5-4d63-ad7f-b48ba236ce3f
Request Id: 274368dd-2bb6-4faa-a0d7-dd9df9d5a652
Cluster Name: WABI-US-EAST2-redirect.analysis.windows.net
Refresh Start Time: April 29, 2019 19:39 UTC
Refresh End Time: April 29, 2019 19:43 UTC
4 Replies
v-yuta-msftCommunity Support
n_young ,
As the error message mentioned, you need to reconstruct the table relationship or remove the duplicate value in 'BillingMonth' column.
Community Support Team _ Jimmy Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Per the other threads with this exact issue, I'm not in control of the underlying data. This is data provided by Microsoft / managed by Microsoft.
For similar threads that don't seem to provide an answer -- https://community.powerbi.com/t5/Service/Microsoft-Azure-Consumption-Insights-BillingMonth-duplicate/m-p/588837?advanced=false&collapse_discussion=true&filter=location&location=forum-board:power-bi-web-app&q=Azure%20Consumption%20Insights&search_type=thread
Other threads appear to get fixed, but it's not clear how or by who.
have the same problem. Can tou tell me if you succeeded to fix the issue. I don't fix the method and documentations.
Thanks by advance for your help
Yes, it eventually got fixed. Below is the eventual solution, summarized from my support engagement that took from May 17th to June 6th to resolve. The majority of the time was spent back and forth getting MS to understand that the problem was with MS data, and not something i was uploading, or in control of in any way. The other complication was that I don't use PowerBI desktop. If you use PowerBI desktop, apparently there's a way to generate your own filtered query to exclude the problematic month, and then upload it yourself to PowerBI Online.
Nevertheless, here's the highlights/summary for you to reference when you put in your support ticket:
- My support Ticket to reference: 119051521001342 - Azure Consumption Insights issue when loading data
- MS Support sent me a new PBIX file configured to exclude the offending month (i think)
- Upload that PBIX file into https://app.powerbi.com via the "Get Data" option.
- Use "My Workspace" and then go to the new "Data set settings" and change the credentials under “Edit settings”.
- This will update the repot with the proper enrollment number.
