Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Outlook Quickfind is Crazy RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    I realize that the Outlook CRM client's quickfind functionality is different than the web client's. I think that's a mistake, since it's confusing and inconsistent for users. However, this post is not about that.

    I have an instance of CRM on-premise with Update Rollup 3 applied to the server and clients. Whenever a user searches for a string starting with SL or SI in the Outlook client's accounts grid, CRM returns every account record in the selected view. For example, if I'm on the "Active Accounts" view, which has 812 records, searching for the string SL or SI returns 812 records. The only column configured as a find column on the Account's Quick Find view is the Account Name column.

    A few other interesting things: it doesn't matter what you type after the SL or the SI, unless it's a special character, which somehow seems to slap CRM back into its senses. For example, you could search for slllikusdhfisuhdfiuwehosduihf and get 812 records. You could search for sihsdsiweuhfisufhiwuehfiuwhfosijfuio and get 812 records. But if you search for slwieuihu;;wouihf, you will get 0 records back, because of the semi-colons in there. Numbers also work like special characters here.

    SL and SI are the only two strings I've found that cause this behavior. Does anyone else have this problem?

    Thanks,

    Andy

    Blog: http://andrewbschultz.com @andrewbschultz
    Wednesday, August 24, 2011 3:54 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi there again,

    I opened a case with Microsoft and this is the solution:

    RESULT:
    The search results are wrong and the data is not filtered correctly.
    For example: searching for "sdkjlfhsdfhiuLANDkhfksfhskh" or any words containing the word “land" returns all records.

    CAUSE:
    This issue happens when field names exist within the search terms. In this case, there is the field with display name “land” causing the issue.
     
    RESOLUTION:
    Method 1:
    Use search syntax like Outlook.
    Instead of searching for simply Erickson, or Erick, use [Last Name]:Erick* or [Last Name]:Erickson
    Instead of searching for simply Alan, use [First Name]:Alan

    Method 2:
    Change display name on the field to be somewhat unique which is not likely to be part of search terms.

    Method 3:
    Set the field which display name containing the search terms to be unsearchable

    This bug is being fixed and will be released in RU9, around July – Sep 2012.

    -------------

    Hope this helps sone of you further.

    Kind Regards,

    Peter

    Monday, March 19, 2012 10:04 AM

All replies

  • Question
    Sign in to vote
    2
    Sign in to vote

     

     

    It is possible that "SL" and "SI" pattern string is present on all the accounts. Can you please verify this? If possible can you share the screenshot of the search result with personally identifiable information erased?

     

    'Find columns' for every entity are customizable. For changing the find column for 'Accounts' entity follow these steps:

     

    1. In CRM go to Settings->Customization->Customizations->Customize the System->Entities->Account->Views

    2. Double click on the 'Quick Find Active Accounts' view and then click on 'Add Find Columns' button to select additional fields for searching

    3. If you want that search result should display this field then click on 'Add View Columns' to include fields in search result.

    4. Then click on 'Save and Close' view and 'Publish Entity Customizations'

     

    Let me know if this works.

     

    Thanks 

    Harshit

     

     

    Wednesday, August 24, 2011 10:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Harshit,

    Thanks for your reply.

    1. No, the strings SI and SL are not present in every account. I can actually search for SIasdiufhiasudgfiaudsfh and return every record in the view. As I said at first, if there are non-alphabetical characters in the string, it doesn't do so - that seems to make it start working correctly.

    2. No, as I said in the first post, the only column configured as a find column on the Account's Quick Find view is the Account Name column.

     

    Thanks,

    Andy

    Blog: http://andrewbschultz.com @andrewbschultz
    Friday, August 26, 2011 1:43 AM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Hey Andrew, me again. Rollup 3 makes changes to the way outlook quick find works. Have you installed it yet?

    One of the fixes in Rollup 3 is this:

    "The search results for system views in the Dynamics CRM 2011 client for Outlook are not compliant with the search results in the Microsoft Dynamics CRM web client."

    This also makes it so you can search on lookups. I don't know if it will fix your issue, but I'd definitely start there.

    Best,
    Phil

    Phil Edry – Altriva Solutions – http://www.altriva.com/AltrivaBlog.aspx
    Friday, August 26, 2011 2:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Phil,

     

    You're a forums champ!

    Yes, I'm working with Rollup 3 installed. I saw that other posting in here and hoped it would help, but it didn't. I actually defined the specifics of this issue after Rollup 3 was installed.

    Thanks,

    Andy

    Blog: http://andrewbschultz.com @andrewbschultz
    Friday, August 26, 2011 12:38 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Hmm, then I'm not sure what else to try. I'm not even sure a server trace would be especially helpful if the issue is in Outlook. I'd suggest starting a support case with clear repro instructions. If it's a bug, a case is the best way to get it fixed in a rollup. I can't repro the behavior it in my environment, but it's Online instead of On-Premises.

    Sorry I couldn't be more help,

    Phil

    Phil Edry – Altriva Solutions – http://www.altriva.com/AltrivaBlog.aspx
    Friday, August 26, 2011 6:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey Andy,

    I am not able to repro on search results issue on my environment.

    But about the second concern regarding the 'Find column' for Accounts entity, by default account name, account number and email address are set as 'find' columns.

    Can you please from 'Customization' that which all columns are checked as 'find' column?

     

    Thanks 

    Harshit

    Friday, August 26, 2011 8:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Harshit,

     

    Yes, I removed Account Number and I believe I removed email address from the find columns. That was the first place I looked for irregularities when this strange behavior was identified.

     

    Thanks,

    Andy

    Blog: http://andrewbschultz.com @andrewbschultz
    Sunday, August 28, 2011 2:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Andrew,

    Since no one has been able to reproduce this, did you find a solution? 

    Regards, Donna

    Tuesday, September 6, 2011 10:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Donna,

     

    No, no solution. All Outlook clients in this organization have this bug.

    Blog: http://andrewbschultz.com @andrewbschultz
    Tuesday, September 6, 2011 4:52 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    and does it happen on more than just the Account entity?  If it is localized to the Account entity, then I would most likely have another close look at that entity.  You might also want to ensure there is no customization running on the entity that might be interfering with the result set that is returned.

    Regards, Donna

    Tuesday, September 6, 2011 8:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Donna,

     

    Thanks for the tips. There isn't any customization on the entity, other than a few custom fields. It seems to be only related to the account. There's not anything on the account that would seem to cause any strange behavior. Especially since, as I mentioned, the error is only occurring in the Outlook quickfind, and not the web client.

    Blog: http://andrewbschultz.com @andrewbschultz
    Tuesday, September 13, 2011 6:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    I have a exact same problem like Andrew have. I would be very thankful If somebody could find solution to this.

     

    Regards,

    Andres

    Sunday, September 18, 2011 4:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the same issue, only that it does not happen on all Outlook installs.

    Just seems the quick find just doesn't work.

    Also, one other item seems weird. Even though in CRM options there is the setting for number of rows to show on each list, the entities show all rows. Even though selected 250 rows for lists, showing all rows (25k+).

    It's been a while since the last message on this. Has anyone come up with solutions or suggestions?


    Tuesday, October 25, 2011 2:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have this problem too.  CRM 2011 - Outlook 2010. I have a custom entity called projects.  The quick find is supposed to find 3 lookup fields, director, owner, and project manager.  Works great in the web version but not in outlook.  However i can search contacts and find the parent customer which is a lookup.  I have all of the rollups applied.
    Thursday, October 27, 2011 7:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have this problem too. Tech support told me it was a known issue with searching custom entities and would be fixed in the enxt rollup, which is due soon.

    - Mark

    Thursday, October 27, 2011 10:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We are experiencing the same problem and have narrowed down the problem a bit. It looks to have something to do with Outlook 2010 and CRM 2011. When searching for a contact and entering "gender" as a search criteria, all the records are returned. It seems that CRM for Outlook 2010 is also looking for fieldnames in the name. When we create a contact with a lastname "basgender" and search for basgender, again all contacts are returned. When we change the lastname to "basgeder" it is working fine.

    When we add the " before and after the search criteria,  so the criteria is "basgender" it is working fine. It seems the query is not parsed correctly. We will see if we can create a case in partnersource,

    Monday, December 12, 2011 9:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Any resolution to this? We have several users that are experiencing the same issue. Rollup 5. Search All Contacts doesnt work when a column is added to the find column

     

    Monday, February 6, 2012 6:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm having the same problem. Added OwnerId as a find column on the Lead entity. Works fine in the browser but it's as if nothing was changed in Outlook. Also on rollup 5. Tried clearing browser cache, restarting Outlook, and rebooting to no avail. 
    Tuesday, February 14, 2012 8:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We also have problems with the quick search in Outlook.
    People here say it's related to Outlook 2010. But we use Outlook 2007 and have this issue.

    In our case the quick search on "Active Contacts" returns all Contacts when you search for any word that contains the substring "chip".
    This is really weird.
    Since so many people have this bug, Microsoft should hurry up and fix this bug as soon as possible.

    - Thorsten

    Sunday, February 26, 2012 2:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    In reviewing these posts, there appears to be a few different things going on.  The one common thread is that many believe they have discovered an issue with the software. 

    If anyone believes they've discovered an issue with the software then I encourage you to open a support ticket with Microsoft.  Opening a support ticket can result in a few things; Microsoft will already be aware of the issue and might have a fix that they can give you for it, MS might not be aware of the issue so they will try to reproduce, MS will troubleshoot the issue and provide you with a fix or something different.

    None of the above can happen unless you open a support ticket.  Forum participants are happy to help answer your questions, share our knowledge, point you to information that might help you, etc. but we can not fix issues with the software.  You will need to open a support ticket to obtain that type of assistance.

    I hope this helps and I am eager to hear what you discovered after opening a support ticket so please return and follow-up.

    Thank you

    Regards, Donna

    Sunday, February 26, 2012 8:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi all,

    We have "the same issue", Outlook 2010, latest rollup 6 installed.

    When searching for "moeland" then I get every contact back as a result. Webclient works fine.

    I suggest that it really searches for the labels too because the form of our contact has a name with the label "Land".

    I will open a ticket with MS now - as soon as I got a solution I will post it here.

    Peter

    Tuesday, March 13, 2012 6:54 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi there again,

    I opened a case with Microsoft and this is the solution:

    RESULT:
    The search results are wrong and the data is not filtered correctly.
    For example: searching for "sdkjlfhsdfhiuLANDkhfksfhskh" or any words containing the word “land" returns all records.

    CAUSE:
    This issue happens when field names exist within the search terms. In this case, there is the field with display name “land” causing the issue.
     
    RESOLUTION:
    Method 1:
    Use search syntax like Outlook.
    Instead of searching for simply Erickson, or Erick, use [Last Name]:Erick* or [Last Name]:Erickson
    Instead of searching for simply Alan, use [First Name]:Alan

    Method 2:
    Change display name on the field to be somewhat unique which is not likely to be part of search terms.

    Method 3:
    Set the field which display name containing the search terms to be unsearchable

    This bug is being fixed and will be released in RU9, around July – Sep 2012.

    -------------

    Hope this helps sone of you further.

    Kind Regards,

    Peter

    Monday, March 19, 2012 10:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Very interesting. I was skeptical about this as well, until I looked and saw that we actually have fields on our account with the labels "SL" and "SI", the two strings I mentioned in my original post here.

    Funny how the special character puts the misbehavior back in its place.

    Thanks!

    Blog: http://andrewbschultz.com @andrewbschultz

    Monday, March 19, 2012 2:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I was at Convergence Houston this week. I talked to a Microsoft Solution Expert and he told me that the problem of Outlook retrieving every record with Quickfind, is known by Microsoft and a fix should be included in the update roll-up 8 (he was not reallly sure which rull-up would have the fix).


    Friday, March 23, 2012 3:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This blog post refers to the behaviour (described by AdmiralConsulting in this thread) of views showing all records rather than user limit:

    http://cognettacloud.com/?p=426

    Looks like pinning the view changes Outlook client behaviour

    Hope this helps. Adam Vero, MCT

    Wednesday, May 9, 2012 2:03 PM