Dynamics 365 On-Premise - Global Search stopped working after December Update

(0) Share

Report

Posted on by Egidijus

Hello everyone,

We've recently upgraded our CRM 2016 on-premise organization to Dynamics 365, December 2016 update for Dynamics 365 was installed, which upgraded our current build version to 8.2.0.749. This lead to Global Search not working, by throwing Query Builder Error, that says that certain entity does not contain a certain field (the missing field is always from related entity that is used in the Quick Find View).

We learned, that this issue is fixed with Service Updates 2, 3, 4 and 5. However since these service updates are only available for online version of the system we find ourselves trapped by either waiting for the next on-premise update, which probably won't be released for the next few months, or by having to remove related entity fields from the Quick Find Views of certain entities, which would not be a good solution since these fields are needed to be displayed while doing regular quick find search.

Has anyone, using Dynamics 365 on-premise encountered this issue and maybe could share their way of solving it?

Many thanks,

Egidijus

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Zohaib Uddin Khan 2,822 on at

Like (1)

Report

I would recommend to raise the MS Ticket and raise your concern to them. Most probably they will share the Hot fix for your Organization. Thanks.

Was this reply helpful? Yes No
Suggested answer

Daniel at VNS on at

Like (1)

Report

Hi Egidijus.

I feel your pain. We're also using on-prem (and do not WANT hosted) and had this same problem after December. After opening a ticket with CRM support and having a CRM-SQL engineer actually tell me 'we aren't SQL experts', I found an engineer that actually knew what he was doing:

Ran this in SQL M/S on CRM DB to check if signature enabled = 1:

SELECT FULLTEXTSERVICEPROPERTY('VerifySignature');

GO

Then ran this to disable it = 0:

EXEC sp_fulltext_service 'verify_signature', 0;

GO

This seemed to fix the problem (which MS said was a 'byproduct of a default SQL installation'). He also said this happens on some CRM deployments and not on others - could not explain why.

We'd also tried disabling full text indexing, which kind of makes global find less useful and it'd fix the problem for a day and then return.

Hopefully this helps you.

Troubleshoot Full-Text Indexing - https://msdn.microsoft.com/ro-ro/library/ms142595(v=sql.110).aspx

Was this reply helpful? Yes No
Suggested answer

PS 23,577 on at

Like (0)

Report

This is a known issue, I think your lead 'quick find view' contains a column from related entities

Here: community.dynamics.com/.../223933

Was this reply helpful? Yes No
Egidijus on at

Like (0)

Report

Hi Daniel,

Thank you for your suggestion. We tried executing the script you mentioned on our CRM DB, however it did not seem to make any difference. Was there anything else to be done regarding this solution?

Many thanks,

Egidijus

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello Egidijus

Tenfold can help in integrating MS Dynamics 365 and enabling click to dial in Outlook. Our click to dial also works on webpages opened in Chrome. They also support MS Dynamics integration www.tenfold.com/.../dynamics

Was this reply helpful? Yes No
Daniel at VNS on at

Like (0)

Report

I know that disabling full text indexing also seemed to fix the problem though it was intermittent. you may want to do that, wait 24 hours, then re-enable, wait another 24 hours and check results.

Was this reply helpful? Yes No