René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Issue: Semantic model refresh completes with warnings due to sort-by-column behavior in Statement file","articleBody":"\nWe’ve implemented our financial statements in Power BI using Bob’s framework from this repo and the accompanying video. It’s a genuinely excellent solution and has worked reliably for us for several years.\n\nStarting on **March 10, 2026**, our semantic model refresh in the Power BI service began returning the message **“Refresh completed with warnings.”** The refresh still succeeds, but this is new behavior and has raised concerns about long‑term stability.\n\n**Suspected root cause**\nWe believe the issue is related to the **Statement file and the use of Sort By Column**, which is critical for maintaining correct statement ordering in the presentation layer.\n\nFor example:\n- ReportSection is sorted by ReportNo\n- Multiple columns rely on explicit sort relationships to render financial statements correctly\n\nThis works cleanly when there is a single statement. As we added additional statements that reuse the same ReportSection values, Power BI continued to work because the sort relationship had already been established. In effect, this “tricked” Power BI into allowing the configuration, even though multiple values now share the same sort key across statements.\n\nOur suspicion is that:\n- A newer version of Power BI Desktop and/or the Power BI Service is now detecting these duplicate sort-by scenarios\n- The service still allows the refresh to complete, but flags it with warnings\n\n**Concern**\nOur primary concern is stability and forward compatibility:\n- Proper sort order in the presentation layer is non‑negotiable for financial statements\n- We’re concerned that a future service update may move from warning to refresh failure\n\n**What we’re trying to do**\nWe’re actively exploring alternative approaches to achieve deterministic sort order for statements without relying on sort‑by-column patterns that may no longer be fully supported or tolerated by the service.\n\nWe wanted to raise this both to:\n- Share what we’re seeing in case others are encountering similar behavior\n- Get guidance or recommendations on more durable sorting patterns for this framework going forward\n\n\u003cimg width=\"766\" height=\"454\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/847070a3-512d-4480-b5ce-0c8f9a7faad1\" /\u003e\n\u003cimg width=\"773\" height=\"427\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c0f85f6d-a1ef-4ce4-95fb-df4ed83238f4\" /\u003e\n\n","author":{"url":"https://github.com/dkillilea","@type":"Person","name":"dkillilea"},"datePublished":"2026-03-11T12:38:46.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/1/FinancialModelling/issues/1"}