Unanswered

Dataverse SEARCH does not return rows in a managed solution, row count = 0

(0) Share

Report

Posted on by Larry2

I have a power virtual agent solution connected to Omnichannel that calls a flow to do a search and row count is always zero. This works in an unmanaged solution in dev but When I import and export to the Prod environment this is where I am having the problem. I tested this with the core table and quick find search isn't returning any matches in the managed solution. I can see in the flow It is finding the table but the search is always zero. I am thinking it is security related but for testing purposes I am system Admin for the environment. Indexes have been deprovisioned and rebuilt, but the results are the same. I also tested with the Dataverse table attached to the solution and as well as adding and populating outside a solution.

Thanks,

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

ChrisPiasecki 6,422 Most Valuable Professional on at

Like (0)

Report

Hi @Larry2,

In the target environment where the managed solution is deployed, you confirmed that Dataverse Search is enabled in the environment settings (via Admin Center), and the table is search enabled?

Also, check on each table the managed property can enable sync to external search index is set to true. Note that any changes to the search index may take several minutes to several hours to sync data depending on the volume of data.

The Search Rows in your flow will run under whatever account you've set on the connection, so the search results will be filtered based on that connection users security privileges in the environment. Make sure that user has necessary read privileges to your tables to see the expected records.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
Larry2 4 on at

Like (0)

Report

All that was verified. I read there were some bugs in Release wave 2 with Quick find in commercial. I am running in GCC. It is working fine as unmanaged code in the dev environment. Not sure if it is related to GCC. The dataverse search is still in preview but works fine in dev GCC and Microsoft said it was OK to go to Prod with the dataverse search.

Was this reply helpful? Yes No
ChrisPiasecki 6,422 Most Valuable Professional on at

Like (0)

Report

Hi @Larry2,

I haven't worked on a GCC environment before so I won't be able to provide much insight specificly around it. That said, the documentation does mention for US Gov environments to enable tables for search in the classic solution explorer:

If you are selecting tables for Dataverse search on a Power Apps US Government environment, use the legacy solution explorer to choose the tables to be indexed for Dataverse search.

Have you tried doing it via this method? If that doesn't help, I'd suggest raising a ticket with Microsoft support since they advised you that it was safe to use it in prod even though it's still preview in GCC.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
Verified answer

MicaelLev 28 on at

Like (0)

Report
Experiencing also problems with Dataverse Search. Your flow uses the Dataverse service and for my part it is the indexing part that is buggy. Here is what I have found and how i am able to fix it temporarly :
The scenario is to deploy a managed solution into another sandbox environment, with quick find views configured.
The Dataverse Search index is turned on.
After deployin, the index columns from the table in question does not change. I suspect Importing managed solution does not update Dataverse Search index.
To fix it :
Add a dumb unmanaged solution beside
Add the table and include only the quick view
Update the view by faking a change by addind another column or watever. Save and publish
In dataverse Search indexing, look at column number, It should have changed now and thus Dataverse indexing will start after a few minutes
Results start to come out.
So, the problem with this scenario is after each "override solution configuration import", the changes will be lost and Dataverse reverts to default index. I have to follow again the described solution...

Was this reply helpful? Yes No