Not comprehensible behavior -> Documents with the same information require different search queries

%3CLINGO-SUB%20id%3D%22lingo-sub-2466051%22%20slang%3D%22en-US%22%3ENot%20comprehensible%20behavior%20-%26gt%3B%20Documents%20with%20the%20same%20information%20require%20different%20search%20queries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2466051%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHi%20all%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20are%20currently%20facing%20an%20unsolvable%26nbsp%3B(for%20us)%20problem%20with%20our%20SharePoint%202019%20installation%20and%20its%20search%2C%20where%20even%20our%20service%20provider%20has%20to%20admit%20defeat.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EBackground%3A%3C%2FSTRONG%3E%3CBR%20%2F%3EWe%20have%20a%20%22parts%20folder%22%20site%20with%20multiple%20document%20libraries%20(for%20each%20document%20type%2C%20e.g.%20technical%20information%20or%20drawing).%20Each%20document%20library%20can%20contain%20different%20file%20types%2C%20but%20usually%20they%20are%20PDF%20files.%20They%20are%20then%20accessed%20through%20a%20single%20search%20page%20with%20a%20customized%20tabular%20result%20template.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EAbout%20the%20problem%3A%3C%2FSTRONG%3E%3CBR%20%2F%3EIt%20does%20not%20always%20return%20the%20correct%20result%20with%20all%20the%20searched%20documents%20for%20certain%20searches.%20Searches%20have%20to%20be%20run%20in%20two%20variations%20to%20get%20two%20partial%20results%2C%20even%20though%20the%20information%20being%20searched%20for%20is%20completely%20identical.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EExample%3A%3C%2FSTRONG%3E%3CBR%20%2F%3EThe%20managed%20property%20%22DTComment%22%20which%20is%20mapped%20with%20the%20crawled%20property%20%22ows_Comment1%22%20is%20searched.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22DTComment%22%20settings%3A%3C%2FP%3E%3CUL%3E%3CLI%3ESearchable%3C%2FLI%3E%3CLI%3EQueryable%3C%2FLI%3E%3CLI%3ERetrievable%3C%2FLI%3E%3CLI%3EAllow%20multiple%20values%20(it%20was%20tried%20with%20and%20without)%3C%2FLI%3E%3CLI%3EToken%20Normalization%3C%2FLI%3E%3CLI%3EFiner%20Query%20Tokenization%20(it%20was%20tried%20with%20and%20without)%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CBR%20%2F%3E%3CEM%3ETarget%20result%3A%3C%2FEM%3E%3C%2FP%3E%3CUL%3E%3CLI%3E15%20documents%20with%20%22DTComment%22%20%3D%20%22New%20Ref.%204.68773%22%2C%20thereof%207x%20.msg%2C%207x%20.pdf%2C%201x%20.dwg%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CBR%20%2F%3E%3CEM%3EActual%20result%3A%3C%2FEM%3E%3C%2FP%3E%3CUL%3E%3CLI%3EWith%20search%20query%20%7BDTComment%3A4.68773%7D%3A%207x%20.msg%2C%206x%20.pdf%2C%201x%20.dwg%3C%2FLI%3E%3CLI%3EWith%20search%20query%20%7BDTComment%3A%20%224.68773%22%7D%20or%20%7BDTComment%3A68773%7D%3A%201x%20.pdf%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CBR%20%2F%3E%3CEM%3EPrevious%20findings%20and%20attempts%3A%3C%2FEM%3E%3C%2FP%3E%3CUL%3E%3CLI%3EThe%20single%20document%20is%20not%20the%20newest%20and%20not%20the%20oldest%20one%3C%2FLI%3E%3CLI%3EIt%20is%20a%20technical%20information%2C%20of%20which%20there%20are%20some%20in%20both%20partial%20results%3C%2FLI%3E%3CLI%3EComment%20removed%20-%26gt%3B%20Full%20Crawl%20-%26gt%3B%20Comment%20copied%20from%20other%20document%20-%26gt%3B%20Full%20Crawl%3A%20Did%20not%20help.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CBR%20%2F%3ECan%20anyone%20explain%20this%20behavior%20to%20me%3F%20And%20maybe%20also%20has%20a%20solution%20for%20us.%3C%2FP%3E%3CP%3EIf%20more%20information%20is%20needed%2C%20feel%20free%20to%20tell%20me.%20Since%20I%20rather%20slipped%20into%20the%20SharePoint%20topic%2C%20I%20still%20lack%20a%20lot%20knowledge.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20in%20advance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2466051%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

Hi all,

We are currently facing an unsolvable (for us) problem with our SharePoint 2019 installation and its search, where even our service provider has to admit defeat.


Background:
We have a "parts folder" site with multiple document libraries (for each document type, e.g. technical information or drawing). Each document library can contain different file types, but usually they are PDF files. They are then accessed through a single search page with a customized tabular result template.


About the problem:
It does not always return the correct result with all the searched documents for certain searches. Searches have to be run in two variations to get two partial results, even though the information being searched for is completely identical.


Example:
The managed property "DTComment" which is mapped with the crawled property "ows_Comment1" is searched.

 

"DTComment" settings:

  • Searchable
  • Queryable
  • Retrievable
  • Allow multiple values (it was tried with and without)
  • Token Normalization
  • Finer Query Tokenization (it was tried with and without)


Target result:

  • 15 documents with "DTComment" = "New Ref. 4.68773", thereof 7x .msg, 7x .pdf, 1x .dwg


Actual result:

  • With search query {DTComment:4.68773}: 7x .msg, 6x .pdf, 1x .dwg
  • With search query {DTComment: "4.68773"} or {DTComment:68773}: 1x .pdf


Previous findings and attempts:

  • The single document is not the newest and not the oldest one
  • It is a technical information, of which there are some in both partial results
  • Comment removed -> Full Crawl -> Comment copied from other document -> Full Crawl: Did not help.


Can anyone explain this behavior to me? And maybe also has a solution for us.

If more information is needed, feel free to tell me. Since I rather slipped into the SharePoint topic, I still lack a lot knowledge.

 

Thank you in advance.

0 Replies