Michael Flanakin
Michael Flanakin
I feel this should be part of 1.0. Right now, it's not clear what value should be used for SkuId. Am I the only one?
Microsoft columns for SKU categorization: - ServiceFamily / x_SkuServiceFamily - MeterCategory / x_SkuMeterCategory - MeterSubcategory / x_SkuMeterSubcategory One related that isn't exactly SKU categorization would be `PublisherType/x_PublisherCategory`. For us, this...
See #608
Aren't there scenarios where there would be multiple types of capacity? We've previously talked about adding SkuDetails column that would be JSON and could have whatever SKU-specific attributes are needed.
As we've discussed SkuId, it includes a region. Including a SkuRegion column is just about making that explicit. As-is, we have scenarios where some charges have a different SKU region...
> Is this a common enough case across providers that is worthy of making it a required column for all rows across all providers? I don't know. I'd need other...
We decided to remove this column from 1.0 because the scenario that it was prioritized for (commitment planning) is more likely to use another data source to get the term.
Updated
I believe you're thinking of `SkuDetails` that was discussed in VS4 (cc @cnharris10). We should do that. But JSON should only be used for uncommon things that aren't primary factors...
> Would you need a SkuTier if the SKUPricingId pointed towards the price that was charged? The finance team would because they don't have the ability to join these two...