Forum Discussion
Intellisense / Auto Complete Stopped Working
I recently uninstalled the store version of PBI desktop to install the direct download version (because I wanted the drag-drop re-order which is not available in the store version). Latest version revision {553CCBE1-56C5-4CF7-BE8D-0AD37CA36E6F}
Intellisense was working fine for a few days, and then became sporadic. Now, it almost never gives the auto-complete for variable/line names. And it rarely shows the matches among built-in functions. e.g. here I would expect table.re to give Table.RemoveColumns among other entries, but it doesn't.
Reinstalled without any affect whatsoever. Turned off Intellisense, restarted, turned on, restarted, and no effect. Is there some cache or some trick someone has for this?
So, I've isolated the problem. Intellisense and auto-complete fail as soon as a 'try' is created without 'otherwise'.
e.g. if you add line 11 from this example anywhere in any query, the feature is broken in all queries.
textUnitPrice = try Number.ToText(Sales[UnitPrice])
5 Replies
- v-diye-msftCommunity Support
- hanseiHelper V
I fail to see the connection between my question about the latest Power BI Desktop and some suggestions for a 7 year old version of Visual Studio.
- v-diye-msftCommunity Support
Hi hansei ,
Based on my test, i cannot reproduce the same issue as you said. Above are some articles for your reference, hopefully give you some hits about the M code.
If does not help, you may submit a support ticket.https://powerbi.microsoft.com/en-us/support/
- hanseiHelper V
It seems that the problem is isolated to a single .pbix file. Others are working fine. Saving a copy (via PBI or Explorer) does not fix the issue. I tried to delete the internal Metadata file, but that made no difference either. Interestingly, Metadata was not even re-created after deletion. Any ideas other than recreating every query?
- hanseiHelper V
So, I've isolated the problem. Intellisense and auto-complete fail as soon as a 'try' is created without 'otherwise'.
e.g. if you add line 11 from this example anywhere in any query, the feature is broken in all queries.
textUnitPrice = try Number.ToText(Sales[UnitPrice])