Copilot (preview) - first attempts

[Jesse_S]

Hi All --

Late this evening I got an email letting me know I was granted access to the Power App Copilot builder. I've been looking forward to experimenting with this and dived in head-first.

First impressions with describing what I wanted and generating the Dataverse table was pretty cool. I managed to get a good approximation for what I going for. What I was mainly interested in seeing was the extent of the Copilot integration into the Power App as a natural language interface to the data.

Unfortunately, after the Power App was generated I was immediately hit with "Something went wrong. Please try again later." Screenshot below to give an idea of the problem.

I spent some time digging around Power Apps Forums, Reddit, DuckDuckGo, and YouTube, but didn't find anything clearly related. I'm curious if anyone here has seen something along these lines yet and if you have any troubleshooting suggestions.

FWIW, I've spent a fair bit of time here:

https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/ai-overview

and here:

https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/ai-conversations-create-app

making sure I'm meeting all the prerequisites.

Thanks & cheers!

[AnthonyAmador]

Hi all, the Product Group team has resolved the error that some of you were experiencing when attempting to use the copilot control. The previous error message stating "Something went wrong. Please try again later." should no longer appear. 

However, if you encounter any new issues or errors with the copilot control, please do not hesitate to open a support ticket with us. This will enable us to track and investigate the issues. 

Thanks for the patience. 
Anthony Amador - Community Support

[dventura]

It is working, however when asking how many Rows of data there are it first said 25, after deleting a few rows containing garbage data it now says 16. The SharePoint List has over one thousand items and I've cut the number of Columns selected down to 4. Not sure why it only searches a few rows but I've had similar results when testing other data sources. 

[mtbaker28]

Reducing the number of SharePoint List columns in the Copilot control got things working for me. It's a fun & interesting way to interact with list data, but we've got a long way to go before this is business ready. There are only 10 rows in my list but Copilot struggles with the most basic "How many are there" and "List values from the column" type questions. It omits some rows from its responses entirely, and can't calculate dates at all (it thinks the current date is "April 2021"). I hope it's just getting warmed up and look forward to more experimentation.

[PASoldier1]

I have tried again this morning and the copilot control seems to be working now. Let the fun begin, I have been waiting in anticipation for this.  

[Lebrass]

Ok so like the rest of you both excel and sharepoint seem to be operational this morning. However also stuck at 18 rows.  I'm using production excel and sharepoint list tables to test with that have 500+ rows, and multiple columns it would be required to read in order for the data returned by copilot to be relevant . I'm hoping those 18 rows its currently stuck at are because they've limited the functionality during preview and not a feature of the production version we'll have to remove columns for to make it functional. 

The exciting bit about the 18 rows I can report back on is that it does show that the suggested questions are much better then they were yesterday without me making any changes to the widget since I logged off. So that already shows some kind of rapid improvement behind the scenes from what i can tell.  

There is a lot of work to be done before this seems to be ready for production, but its heading in the right direction. Using smaller sample Dataverse data Copilot generated when it makes an app that is under that 18 row max seems to work great so far.

Hoping that we can continue to use this thread to share updates and tips on how to increase the functionality we're all getting because it has helped a lot.

[dventura]

Any updates on this issue? I'm still stuck at 18 results like @Lebrass.

[gilmara]

I keep asking it "how many rows in this dataset". Yesterday it said 22, today it says 24. There are actually 160, so I guess we're making progress.... I submitted a service request with Microsoft. Haven't received a response yet. 

[Lebrass]

Still stuck at 18 rows over here still, with more then 500 rows, and 4 required columns on my test table.

[PowerGR050]

I am not getting the "Something went wrong" message anymore, but the copilot is not working at all. it doesnt do anything.

[Lebrass]

What datasource did you hook in after you added the widget to your workspace?  It may be related to whatever source you used?  It seems to be a work in progress very much still. Last week my test table with 700 rows only registered 18 rows on copilot. This week the same unchanged table only registers 17 rows.