Documentation :: How to upgrade to FOCUS 1.2 schema? #1909
-
|
I have installed the FinOps Toolkit using the dataset version 1.0r2 as the 1.2 was in preview 
I now realise that the FinOps toolkit is compatible with the 1.2. How to upgrade? (The FOCUS 1.3 is also out now so I think this sort of update will happen quite frequently in the future) |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
|
Should I first remove all the 1.0r2 data form the ADX and then re-import all the data in DOCUS 1.2? |
Beta Was this translation helpful? Give feedback.
-
|
Should I re-deploy all the Power BI? |
Beta Was this translation helpful? Give feedback.
-
|
Cost Management exports don't allow you to change version after the export is created. The only way to do this is to delete the export and create a new one. I would recommend backfilling the historical data as well when you do that. The cleanest way to do that is via PowerShell, but you can do it manually in the UI or even via ADF. https://aka.ms/ftk/Start-FinOpsCostExport When hubs sees the new dataset for a month that was already ingested, it should overwrite the data. There are explicit checks for the scope and month to ensure we don't keep data when exporting newer datasets. |
Beta Was this translation helpful? Give feedback.
-
This is not completely true.
Basically this is what happens:
|
Beta Was this translation helpful? Give feedback.
-
|
Before: 
After: 
|
Beta Was this translation helpful? Give feedback.
-
|
But now I have a doubt @flanakin, How can I check in ADX if the export is really the 1.2-preview? |
Beta Was this translation helpful? Give feedback.
Cost Management exports don't allow you to change version after the export is created. The only way to do this is to delete the export and create a new one. I would recommend backfilling the historical data as well when you do that. The cleanest way to do that is via PowerShell, but you can do it manually in the UI or even via ADF.
https://aka.ms/ftk/Start-FinOpsCostExport
When hubs sees the new dataset for a month that was already ingested, it should overwrite the data. There are explicit checks for the scope and month to ensure we don't keep data when exporting newer datasets.