Senior-authored Markdown
# Conclusion The connected Power BI Desktop model is a small Import semantic model. Its business-facing structure is a ledger star: `Ledger` relates to `Account` and `Calendar`. `Metrics` contains four measures. Two hidden calculated date tables are also present. ## Model inventory | Table | Observed contents | Storage | |---|---|---| | `Account` | 3 columns | Import | | `Calendar` | 3 columns | Import | | `Ledger` | 4 columns | Import | | `Metrics` | 1 placeholder column and 4 measures | Import | | `DateTableTemplate_4a3e593b-a196-4a2f-9343-f7dc0519ce56` | 7 hidden date columns | Import; calculated partition | | `LocalDateTable_88a1fec1-b827-4666-af6e-18472a67bc31` | 7 hidden date columns | Import; calculated partition | The audit summary reports six tables, 31 columns, four measures, six partitions, three relationships and zero security roles. ## Business-facing columns | Table | Column | Data type | Observed metadata | |---|---|---|---| | `Account` | `AccountKey` | Int64 | Summarise by None | | `Account` | `AccountName` | String | Summarise by None | | `Account` | `AccountType` | String | Summarise by None | | `Calendar` | `DateKey` | Int64 | Summarise by None | | `Calendar` | `Date` | DateTime | Format `yyyy-mm-dd`; summarise by None | | `Calendar` | `FiscalMonth` | Int64 | Summarise by Sum | | `Ledger` | `DateKey` | Int64 | Summarise by None | | `Ledger` | `AccountKey` | Int64 | Summarise by None | | `Ledger` | `SignedAmount` | Decimal | Format `$#,0.00;($#,0.00)`; summarise by Sum | | `Ledger` | `IsAdjustment` | Boolean | Summarise by None | | `Metrics` | `Placeholder` | String | Summarise by None | ## Measures The following qualified measure names and currency formats were observed: - `Metrics.Actual Net` - `Metrics.Actual Revenue` - `Metrics.Budget Net` - `Metrics.Net Variance` Exact DAX expressions were not returned by the bounded reads used for this build, so production definitions and intended status remain unknown. ## Relationships All three observed relationships are active, many-to-one and one-direction: 1. `Ledger.DateKey` → `Calendar.DateKey`. 2. `Ledger.AccountKey` → `Account.AccountKey`. 3. `Calendar.Date` → `LocalDateTable_88a1fec1-b827-4666-af6e-18472a67bc31.Date`. The third relationship and hidden date tables indicate that automatic date/time behaviour coexists with the explicit `Calendar` table. ## Review observations - `Calendar.FiscalMonth` is configured to summarise by Sum even though the target declares it as a month number. Summarise by None should be assessed; no change decision is recorded. - The intended strategy for the explicit `Calendar` table versus automatic date tables is not recorded. - Zero security roles were reported inside this model snapshot. Production security requirements outside the snapshot remain unknown. - `Ledger.JournalSource` and `Ledger.ApprovalStatus` were not observed among the four audited `Ledger` columns. A separate consultant source reports upstream availability; it does not alter this audit observation.