Hi Yuri,

Im having the same issue and finding myself going round in circles.

Did you get anywhere towards resolving this?

Lewis

So i got to the bottom of this one. (Or my colleague did)

Here is my custom index class, as well as the but that needs adding to the composer.

public class MyCustomIndex : UmbracoContentAzureSearchIndex
{
    public MyCustomIndex (
        ILoggerFactory loggerFactory,
        string name,
        LicenseManagerCollection licenseManager,
        IOptions<ExamineXConfig> config,
        IOptionsMonitor<AzureSearchIndexOptions> indexOptions,
        IOptions<AzureSearchOptions> azureSearchOptions,
        IServerRoleAccessor serverRole)
        : base(loggerFactory, name, licenseManager, config, indexOptions, azureSearchOptions, serverRole)
    {
    }
}

builder.Services.AddExamineXAzureSearchIndexFromUmbraco<AzureSearchFilterIndex>("MyCustomIndex");

So going from normal Examine (disc) to ExamineX, you can update your custom index to inherit UmbracoContentAzureSearchIndex and update your composer to use AddExamineXAzureSearchIndexFromUmbraco.

In case anyone is interested in the topic, here is very basic Umbraco solution with custom ExamineX index configuration - github

Thank you, this helped! I'm evaluating ExamineX and my 100 allowed items were taken up by media items so I was able to exclude them from the ExternalIndex pretty easily.

Hi all - We will update the documentation for custom indexes today.

Its actually easier than what is listed above and you don't need to inherit from UmbracoContentAzureSearchIndex.

For custom indexes with Examine, you can continue to inherit from the normal/documented index types based on the Umbraco docs https://docs.umbraco.com/umbraco-cms/v/10.latest-lts/reference/searching/examine/indexing

Then, to opt your custom index into ExamineX (probably based on your environment type like 'prod'), you can just do:

• For Umbraco Content based indexes (i.e. UmbracoContentIndex/IUmbracoContentIndex):

  • builder.Services .AddExamineXAzureSearchIndexFromUmbraco<UmbracoAzureSearchContentIndex>("YourIndexName")

• For non-Umbraco custom indexes based on custom data sources (i.e. UmbracoExamineIndex/IUmbracoIndex):

  • builder.Services .AddExamineXAzureSearchIndex<AzureSearchIndex>("YourIndexName")

Docs updated for custom indexes https://examinex.online/customization#custom-indexes

I am really struggling to get this to work. I followed the umbraco code to the letter and have it working perfectly with local indexes.

I have a custom index which only needs a few custom properties based on the content being indexed (such as converting a location to lat/long for example).

However when I try to switch it to an ExamineX index (which are working for Internal/External indexes) I get a load of different issues:

• object reference not set errors when running the IndexItems code in the populator
• sometimes index simply does not populate with no errors being logged
• when publishing content, the custom fields are not being indexed, instead the umbraco properties

Can I confirm whether the existing line of config should be removed....or should both lines exist? The documentation could be interpreted either way.

Should any other code changes be required to swap from a local to azure index using ExamineX? A full code example would be very useful, that works both when building an index and publishing content with custom fields being added in the valuesetbuilder.

You should remove the AddExamineLuceneIndex call and only leave the ExamineX call. There are 2 different ExamineX calls depending on whether your custom index is of type UmbracoContentIndex/IUmbracoContentIndex (AddExamineXAzureSearchIndexFromUmbraco) or UmbracoExamineIndex/IUmbracoIndex (AddExamineXAzureSearchIndex).

Thanks, that's what I'd originally tried but just get the errors/issues mentioned.

I'm assuming it's the 'umbraco' one I need but it seems to just use the full set of umbraco content properties when publishing a node.

Using the 'custom' one breaks the back office Examine dashboard.

@Shannon I am helping Sue work through this issue, not sure if its just the application in general but i stripped the index creation back as we have spoken before about the setup. As we have also discussed, if its not working on Azure then stripping it back to the local indexes is a good place to start, which i have done but having a very odd issue.

We use the setup below in a couple of different Umbraco installs and its fine, so its very odd, but we are not getting any feedback from Examine / Umbraco to understand if anything is failing as if it is, its doing it silently.

Basically we have:

• A ConfigureWebsiteIndexOptions class which inherits IConfigureNamedOptions as we have some custom field definitions
• A WebsiteIndexerComponent class that Initializes the TransformingIndexValues method and a composer to register it

Startup has this code:

        services
        .AddExamineLuceneIndex<UmbracoContentIndex, ConfigurationEnabledDirectoryFactory>(SearchKeys.WEBSITE_INDEXER)
        .ConfigureOptions<ConfigureWebsiteIndexOptions>();

The WebsiteIndexOptions Gets fired, the WebsiteIndexerComponent gets fired and i can see it registering the event handler but whilst the index is created, it has no records and no fields.

If we try and publish the index, nothing happens (we had the same issue with ExamineX Azure for this setup, no logging apart from the initial index rebuild notification).

But, if i publish a record with a document type that is allowed to be indexed by this custom index, it actually hits the TransformingIndexValues method and adds that record to the index.

Its like the index is being provisioned but not correctly wired up to anything, but the system knows about it because publishing an item pushes that item into the index. We have had issues before with nothing firing, but i don't think we have ever had an issue where it only fires for publishing. I may attempt to create a blank Umbraco project and point to the database and just migrate the index code, but is there any specific reason why this could be the case?

is working on a reply...