A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data
Dear @Marion Berg,
Thank you for reaching out regarding the issue with duplicate measures in Excel. From my research, I found one closely related case reported in February 2026 following a Windows update. In that case, the issue was resolved after the affected users applied the next set of Windows and Microsoft 365 Apps updates.
For reference, here is a related discussion describing the same behavior: Duplicate Measures in Excel – Tabular Model 1600 - Microsoft Q&A
Your testing results further confirm that this is build-specific:
- Broken: 2602 (19725.20170) and 2508 (19127.20570)
- Working: 2602 (19725.20172)
These builds were released around March 10 across the Monthly Enterprise, Current, and Semi-Annual Enterprise Channels. It appears that the March 18 Windows update deployed an unstable variant to some machines, while others received the fixed build (.20172) or a newer March 17/18 release.
I recommend updating Excel to the latest available build for your channel:
- Open Excel > File > Account > Update Options > Update Now.
- Let it download and install (it will likely go to Version 2602 Build 19725.20190 for Current Channel users, or the latest available in your channel).
- Restart Excel completely.
- Reconnect to your SSAS Tabular model and refresh the PivotTable Fields list.
In the February case referenced above, the issue was resolved immediately after completing these steps. The newer build (.20190) is already available and should move your installation beyond the affected .20170/.20172 builds.
For reference: Update history for Microsoft 365 Apps (listed by date) - Office release notes | Microsoft Learn
For Version 2508 (Semi-Annual Enterprise Channel) users
Updates are released more slowly in this channel. If a newer build is not available immediately through automatic updates, the recommended approach is to wait for the next Semi-Annual rollout. Microsoft typically backports fixes quickly for regressions like this.
If the issue persists even after updating, I recommend that the Global Admin in your organization create a service request with Microsoft Support. A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis. Ask The Global Admin in your organization to create a service request with Microsoft support to get advanced technical assistance and diagnostics. For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin. If you don't know who your IT administrator is, please refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support
I hope this helps clarify the situation and provides a practical path forward. Should you have any further questions or need additional assistance, please don’t hesitate to reach out. I’m always happy to help. Wishing you a wonderful day ahead.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.