You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refreshing the WorkloadOptimization PowerBI in FinOps 0.6 I get an error on all tables of:
"Load was cancelled by an error in loading a previous table."
Looking down at the Resources section there's an error of:
Column 'id' in Table 'Resources' contains a duplicate value '/subscriptions/SubID/resourceGroups/RGName/providers/Microsoft.HybridCompute/machines/VMName/extensions/AzureMonitorWindowsAgent' 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.
More than likely this was one of our Arc enabled virtual machines that got rebuilt with the same name and had the Azure Monitor Agent extension reinstall. A pretty common situation. Is there any way I can resolve this myself or can logic be added in future implementations to consider this scenario?
The text was updated successfully, but these errors were encountered:
Refreshing the WorkloadOptimization PowerBI in FinOps 0.6 I get an error on all tables of:
"Load was cancelled by an error in loading a previous table."
Looking down at the Resources section there's an error of:
Column 'id' in Table 'Resources' contains a duplicate value '/subscriptions/SubID/resourceGroups/RGName/providers/Microsoft.HybridCompute/machines/VMName/extensions/AzureMonitorWindowsAgent' 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.
More than likely this was one of our Arc enabled virtual machines that got rebuilt with the same name and had the Azure Monitor Agent extension reinstall. A pretty common situation. Is there any way I can resolve this myself or can logic be added in future implementations to consider this scenario?
The text was updated successfully, but these errors were encountered: