I am currently pulling some data from a BCS connection to populate custom properties on my user profiles. I know that piece is working since I am able to look up a user in CA, Application Management -> User Profiles Service -> Manage User Profiles. When I look up a user there I can see the values I expect. I also have a Powershell script that allow me to pass in a logon, then see all the property values I expect. This is on a 2010 farm
I have also mapped managed properties to the crawled properties. The curious thing here is that when I added the Managed Property,then mapped to a crawled property I came across multiple instances of the crawled property. For example I found the same property among the Business Data, and People categories. To make sure I added both as mappings to the Managed Property.
My expectation at this point was to go into the People Search Core Results web part, add my new properties to the Fetched Properties field () and see the data. I have set the xsl to show the raw xml data, and know I will have to modify the default xsl to see my new properties. I can see the node for my custom properties, but they are empty, self closed, nodes.
One thing that popped out at me was that when I modified the Powershell script that iterates over all the properties, oob abd custom, and try to see the ManagedPropertyName and IsSearchable properties for the properties, they are both null. Naturally I have run the search that should pick up the property values with no problems, and even added one foe the business data.
What am I missing here?

0 commentaires:
Enregistrer un commentaire