Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am not able to search through Global Search in CRM Customer Service Hub App.
Please find the screenshot.
Could any one have any idea ?
Same issue here so seems like a general issue. We logged an MS ticket but no response yet.
Could you please let me know once you get any resolution.
On our end the issue seems to be resolved. I think they did something in the background.
we're seeing the same issue (EMEA region), also started after the latest Service Update - just opened a ticket with support to get it fixed.
A quick call with Support fixed the issue for us:
If you do nothing, this will be fixed by a process that the engineering team has started and is currently being rolled out, but it might take some time to reach your environment.
What we did is to disable and re-enable the Relevance Search (Power Platform admin center -> select your affected environment -> settings -> search for "relevance"), which will result in the search engine being reprovisioned. You can check that through <environment url>/api/search/v1.0/status , it should report status as provisioned once it's fixed.
Its a known issue from our side and the fix has been deployed in your region. Please confirm is it working or not?
We also had the issue and after the fix we noticed that our DB capacity has increased from 8 GB tot 22 GB for the relevance search entity. On our side we have not changed anything to the fields / entities part of the relevance search.
I logged a ticket at support but they state it is "normal behavior" because of data maybe not being indexed properly before. But this seems strange as we never had issues before with the search.
Any one else with the search issue also experienced a big increase in DB capacity?
Business Applications communities