On iOS, I was not able to get it to work. I was unable to do a voice search on my windows phone, even though the identical search phrase worked on Surface Pro 3.Ī lot of people miss the last one, which makes it easier to validate wheter the configuration works. If I type, I usually see the result suggestions later on the screen, and at least can select. When I use voice, I cannot control when the search request is sent, and it seems to be to fast to find suggested results in PowerBI. Like I said earlier, it seems to be also a timing problem. Try typing the Natural Language query and wait for results of PowerBI to show. Create Cortana Pages in PowerBI and add the question phrases (to increase 'matches' in PowerBI). Enable Cortana search on the dataset in PowerBI Connect work or school account in Cortana Connect work or school account in windows It seems to be that the requirements to work are: It also does not change the 'best match' if PowerBI provides a better content match, but provides that slower. It seems that 'best match' is weighed a lot in favor of time rather than completeness. The biggest issue I have on these two devices is the 'best match' which a lot of times finds a 'best match' on the web before it finds it in PowerBI. I also have it running on a Lumia 830 with Version 1511 of Windows Mobile. I got it to work with Windows 10 build 10586 on A Surface Pro 3.
0 kommentar(er)
