Timeline for How a Property name inside my search query can referecne different site columns from different site collections
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2016 at 13:43 | vote | accept | John John | ||
| Sep 28, 2016 at 21:46 | comment | added | John John | .... it mentioned that when building crawled properties the white spaces will be removed, then it will be prefixed with ows_q_. So actually the three site columns in my case “item Number” & 2 “ItemNumber” are being represented by a single managed property , which is ows_q_txt_ItemNumber ?? please check my edit where i provided how my crawled properties are defined.. | |
| Sep 28, 2016 at 21:45 | comment | added | John John | So based on this could the senario I faced is as follow. Now I have define three site columns inside 3 different site collections ; which have the following INTERNAL names Item_X0020_number & ItemNumber & also ItemNumber. Now I got the following internal name “Item_X0020_number” since using the UI I defined the site column named to be “Item Number”. so as a result I got a single crawled property named ows_q_txt_ItemNumber representing the 3 site columns, because in this link technet.microsoft.com/en-us/library/jj613136.aspx | |
| Sep 28, 2016 at 20:35 | history | answered | Matthew McDermott | CC BY-SA 3.0 |