Hi,

By default only PageData and UnifiedFile "getters" are registered. If you want to add a "getter" for your block use:

SearchClient.Instance.Conventions.UnifiedSearchRegistry.DefaultProjectionBuilder.ProjectOriginalObjectGetterFrom<MyBlock>(b => () => GetBlock((IContent) b).ContentLink));

static MyBlock GetBlock(ContentReference contentLink)
        {
            var contentRepository = ServiceLocator.Current.GetInstance<IContentRepository>();
            return contentRepository.Get<MyBlock>(contentLink);
        }

Hi Adam,

This is because we do not do any projections for blocks out of the box. This is ofc possible to extend. I will provide you with some code so you hopefully can make it work.

First you need to add the convention for the projection:

instance.Conventions.UnifiedSearchRegistry
                .Add<BlockData>()
                .PublicSearchFilter(c => c.BuildFilter<BlockData>().FilterOnReadAccess())
                .CustomizeProjection(CustomizeProjectionForBlockData);

After that you need to add the extension methods to make that work:

private static HitProjectionBuilder CustomizeProjectionForBlockData(HitProjectionBuilder projection)
        {
            return projection.ProjectOriginalObjectGetterFrom<BlockData>(b => () => GetBlock(new PageReference(((IContent)b).ContentLink.ID, ((IContent)b).ContentLink.ProviderName)));
        }

  And:

private static BlockData GetBlock(ContentReference contentLink)
        {
            var contentRepository = ServiceLocator.Current.GetInstance<IContentRepository>();
            return contentRepository.Get<BlockData>(contentLink);
        }

Hope that will help you on the way. And if there is anything else just let me know

Thanks Guys - Marcus, I am trying your example. I am having a compile issue with "c.BuildFilter<BlockData>".

'EPiServer.Find.IClient' does not contain a definition for 'BuildFilter' and no extension method 'BuildFilter' accepting a first argument of type 'EPiServer.Find.IClient' could be found (are you missing a using directive or an assembly reference?)

Is this an extnetion already included in Find or one I need to create it?

Hi,

Yeah the extension already exist. It resides in the namespace EPiServer.Find in a class called ClientExtensions. Myabe need to add a using?

/Marcus

Perfect - That was it! Thanks Marcus

Hi,

I thought I'd just add some info in case someone else stumbles upon this thread.

Blocks aren't included in unified search out of the box as they typically shouldn't show up individually in search results (there's nothing to link to etc). They can however be included on their "host" pages making them searchable inside of the pages that they are used on. See here for more info.

With that said there are of course use cases where one would want to include blocks in unified search, like in this thread. If blocks, or any other type is included it may be cases where you want to exclude them from certain search functionality. That can be done using a filter, like:

Filter(x => !x.MatchTypeHiearchy(typeof(BlockData))