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
x_CommitmentDiscountSpendEligibility and x_CommitmentDiscountUsageEligibility are declared in the FOCUS 1.2 Costs schema, projected by Costs_v1_2(), surfaced as Power BI fields, and documented as charge-level values β but the transform hard-codes both to an empty string. Anyone who follows the documentation gets blanks and no error.
The two agent-facing surfaces are the most likely to hit this: the Copilot Studio knowledge file tells the agent both columns are available on Costs_v1_2(), and the Power BI field list shows them alongside populated columns.
π£ Repro steps
Deploy a FinOps hub and ingest cost data.
Run the following against the hub database:
Costs_v1_2()
| summarize Rows = count() by x_CommitmentDiscountSpendEligibility, x_CommitmentDiscountUsageEligibility
A single row is returned, with both values empty.
Run the same summarize against Prices_v1_2() for comparison β it returns Eligible / Not Eligible.
π€ Expected
Either behavior would be consistent; today's is not:
Populate them. Look the meter's eligibility up per cost row, the same way the Prices side resolves it. This is already tracked as an unchecked item in [Hubs] Data ingestion transform changesΒ #1111 under Costs (FOCUS cost): "Feature: Add CommitmentDiscountSpend/UsageEligibility".
Or stop advertising them. Drop the columns from the Costs schema, Costs_v1_2(), the Power BI dataset, the data dictionary, the data model, and the agent knowledge file, so nothing offers a column that is always blank.
If populating them is the plan but not imminent, an interim note in the data dictionary and the agent knowledge file would stop consumers building on an empty column.
βΉοΈ Additional context
This issue covers only the discoverability mismatch β documented and exposed versus always empty. The implementation itself is the existing [Hubs] Data ingestion transform changesΒ #1111 line item; splitting it out here because the docs, Power BI, and agent surfaces need attention regardless of when the transform is filled in.
π Problem
x_CommitmentDiscountSpendEligibilityandx_CommitmentDiscountUsageEligibilityare declared in the FOCUS 1.2 Costs schema, projected byCosts_v1_2(), surfaced as Power BI fields, and documented as charge-level values β but the transform hard-codes both to an empty string. Anyone who follows the documentation gets blanks and no error.In FOCUS 1.0 the Costs dataset doesn't define the columns at all β they exist only on the Prices side. So the two versions disagree as well.
Where the columns are advertised
''IngestionSetup_v1_2.kql#L796-L797IngestionSetup_v1_2.kql#L992-L993Costs_v1_2()query functionHubSetup_v1_2.kql#L277-L278IngestionSetup_v1_0.kqldata-dictionary.md#L84data-model.md#L305-L306Costs_v1_2Costs.tmdl#L1724Costs_v1_2()schema-reference.md#L126-L127The two agent-facing surfaces are the most likely to hit this: the Copilot Studio knowledge file tells the agent both columns are available on
Costs_v1_2(), and the Power BI field list shows them alongside populated columns.π£ Repro steps
Deploy a FinOps hub and ingest cost data.
Run the following against the hub database:
A single row is returned, with both values empty.
Run the same summarize against
Prices_v1_2()for comparison β it returnsEligible/Not Eligible.π€ Expected
Either behavior would be consistent; today's is not:
Costs_v1_2(), the Power BI dataset, the data dictionary, the data model, and the agent knowledge file, so nothing offers a column that is always blank.If populating them is the plan but not imminent, an interim note in the data dictionary and the agent knowledge file would stop consumers building on an empty column.
βΉοΈ Additional context
CommitmentDiscountEligibilityADX table loaded from the Commitment discount eligibility open data file. If that merges, populating the Costs side becomes a lookup against that table, so the two are worth sequencing together.x_CommitmentDiscountSpendEligibilityis always'Not eligible'Β #1593 (closed) covered the related case of the Prices column always readingNot eligible.