web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

Do I update Dataverse Search fields in Production or Sandbox? Confused by this.

(0) ShareShare
ReportReport
Posted on by 75

I was always told to use Sandbox for all customizations and never Production.  I'm trying to customize Dataverse Search and I see under the solution where I add tables to be included, and it's clear that you modify the "Quick Find View" and add "Find by" fields to have those included, and that's fine.

Here's where I'm confused though.  In Sandbox, I edit the "Quick Find View" of a few tables and add the fields I want.  Everything works fine in Sandbox.  I export the solution as managed, and then import it into Production.  Nothing happens, nothing changes.  I go into the solution in Production and it shows 0 tables included in Dataverse Search, so completely ignores the solution I imported.

That to me means you must modify it in Production and not Sandbox, but then that means I'd be editing all these "Quick Find Views" in Production and not Sandbox.  I've never modified anything directly in Production, is that correct?  Shouldn't it have updated it based on importing the solution from Sandbox?

It doesn't matter what changes I make to the solution in Sandbox for Quick View or tables to include in Dataverse Search, it never updates Production when importing the solution.

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    on at

    Hi psychobunny83,

    I tested this on my side and it could work fine.

    In one environment, I added the Created By(User Name) column of Account Quick Find View.

    pastedimage1661159030919v1.png

    Then I created a new solution and Add "Account" entity and only select this view:

    pastedimage1661159170906v2.png

    Then I export it and import into another environment, this field is checked:

    pastedimage1661159227019v3.png

    You could only add that Quick Find View to have a try.

  • Suggested answer
    Bipin D365 Profile Picture
    28,983 Moderator on at

    Hi,

    Are you importing managed or unmanaged solution to production?

    If managed have you tried increasing version of the solution then import.

  • psychobunny83 Profile Picture
    75 on at

    That part works, I'm referring to the "Dataverse Search" screen, this one here https://imgur.com/a/hsCB9TB

    If I customize the tables to include in the solution in Sandbox and then import to Production it doesn't update Production.

  • psychobunny83 Profile Picture
    75 on at

    I'm importing managed into production, the version always increases any time I export from sandbox, but it's this screen here I'm referring to https://imgur.com/a/hsCB9TB

    No matter what I change in sandbox, I import into production and this never updates.  I can remove Accounts for example in sandbox, upload to production, and it still shows Accounts checked off.

  • Suggested answer
    Bipin D365 Profile Picture
    28,983 Moderator on at

    Hi,

    This has to be configured in solution sandbox instance. Please check below article

    docs.microsoft.com/.../configure-relevance-search-organization

  • psychobunny83 Profile Picture
    75 on at

    So then it's a bug when I export the solution from sandbox and import it to production and it does nothing?  Microsoft support has not been helpful with this at all so it's really frustrating.  I've already read that document many times, it doesn't really explain much.  I can add 10 tables to the index in the sandbox solution, yet when I import it into production there's only 5 tables showing in the solution as being part of the index.  I think we will just disable relevance search as it's super buggy.

  • jim.corriveau@chesterton.com Profile Picture
    81 on at

    psycobunny83,

    Just for laughs, when you added the entity to the solution did you select to include meta data?  I'm just guessing that Dataverse Search settings maybe considered meta data of the entity and not part of any view or other object in the entity.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 108 Super User 2025 Season 2

#2
Jimmy Passeti Profile Picture

Jimmy Passeti 50 Most Valuable Professional

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 49 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans