Forum Discussion
Analyse in Excel issuing invalid MDX
We have a scenario in Analyse in Excel where if a user deselects some items from a filter in a pivot table, Excel is issuing invalid MDX. It is placing the MDX except operator (-) in the wrong position with respect to the curly braces denoting the set.
Has anyone seen this before, it is becoming very common.
Query(1, 90) The syntax for '<ccon>{</ccon>' is incorrect
5 Replies
- grazitti_sapna
Super User
Hi JosAsh,
This is a known issue with Analyze in Excel + MDX generation, especially when users manually deselect items in Pivot filters.
Try below fixes:-
1. Avoid deselecting, use selecting (Clear all filters and then select the required Items)
2. Use Slicers instead of PIVOT filters
3. Reduce heirarchy complexity (remove and deep parent child relationships)
4. Reduce the no. of rows to be analysed
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!- Lodha_Jaydeep
Solution Sage
Hi JosAsh,
Could you let us know if the issue is now resolved or if you are still experiencing any problems? Please feel free to provide an update if you need further assistance.
nicgAdvocate II
I am seeing the exact same behavior for users in Europe, but nowhere else it seems. Feels like a localization bug introduced in a recent Excel version. Here is the version they are running: Microsoft® Excel® for Microsoft 365 MSO (Version 2603 Build 16.0.19822.20086) 64-bit
v-hashadapuCommunity Support
Hi JosAsh , Thank you for reaching out to the Microsoft Community Forum.
From what I heard, this is observed by some other users too. I suggest you avoid deselection, clear and select instead or use slicers, which don’t hit this pattern as often. If it’s impacting users regularly, it’s worth raising a Microsoft Support ticket with your Excel version and a reproducible example, they may help you clear this issue.
Below is the link to help create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn- v-hashadapu
Hi JosAsh , hope you are doing well.
Just wanted to know if your issue has been resolved through your support ticket with Microsoft? If so, we would greatly appreciate it if you could share the insights here, as they may benefit others with similar issues.
If you have any other queries, please feel free to raise a new post in the community. We are always happy to help. Thank you.
