I have a scope defined that targets an external content type (exposed through a BDC service). All was working fine until yesterday when the number of results doubled and half the urls start with the bdc3:// protocol; the other half are the original results that have always been there. I need to get rid of these extra links.

So far I tried the following which did not work:

  1. Went into the ETC's BDC Connectivity service for the ETC and recreated the profile page (note that I already had a custom action set for defining the url I want).
  2. In the search service, I did an index reset
  3. I did a full recrawl of the content source for my ECT.

How do I get rid of these?


MOVED FROM COMMENT BY @chris-m (marked as CW)

Solution: Turns out the issue was caused by the configuration of the scope rule, ContentSource = NameOfContentSource (which we had incorrectly named after the ECT).

The name was misleading because a content source represents an external data source not an individual ECT.

Over time we added several ECTs that all used the same external data source (& only one of them used profile pages w/ an alternate action, hence the bcd3:// links).

To resolve the issue we changed the scope rule to: CustomPropertyName = ContentTypeName after having mapped the crawled property 'EntityName' to CustomPropertyName.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.