Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the column name
PricingModelto its correct versionpricingModelfor the MCA file schema, which is actually what is provided in the file when obtained through Exports (small letter p instead of capital P).This distinction is important to address a use case where one would attempt to append a usage data in the EA format, which is:
azure-docs/articles/cost-management-billing/dataset-schema/cost-usage-details-ea.md
Line 55 in 97ad002
The EA format uses
PricingModeland appending this to the MCA format to perform a continuous cost analysis across months before and after change to MCA will not be successful.I do not know if previous versions of the MCA schema did actually use
PricingModelas I cannot prove this through Exports, so I am only updating the most recent version of the schema