Azure Search task processor broken

The workaround is to move back to an older version of the Azure Search package. There are also options to configure our search fields as well and make them do what you're looking for.

Check out the 2 global events:

DocumentFieldCreator.Instance.CreatingField.After += CreatingField_After;
DocumentCreator.Instance.AddingDocumentValue.Execute += AddingDocumentValue_Execute;

Here's something you can do to in the CreatingField_After event:

if (field.Name.Equals(nameof(TreeNode.NodeLevel), StringComparison.OrdinalIgnoreCase) ||
    field.Name.Equals(nameof(TreeNode.NodeOrder), StringComparison.OrdinalIgnoreCase))
{
    field.IsSortable = true;
    field.IsFilterable = true;
}

Unfortunately, that is not a real workaround - we need to use the newer Azure Search API which is not supported with the Kentico Libraries version of Microsoft.Azure.Search.

Similarly, the search index is entirely custom (full-text pdf search of CDN hosted reference materials associated with Kentico hosted products), so a global event handler won't fit the bill.

As an aside, the entirety of Microsoft.Azure.Search is deprecated and is supposed to be replaced by Azure.Search.Documents.

Although, that gives me an idea: might be able to workaround by using the Azure.Search.Documents library side-by-side with the Kentico supported, but deprecated Microsoft.Azure.Search.

Would be great if Kentico would release a hotfix supporting either the latest deprecated Microsoft.Azure.Search or switching to the correct Azure.Search.Documents...

Understood. Then the problem becomes if Kentico doesn't support the newer library you need to use, then you need to work with Kentico to make that work or find another solution.

If the index is entirely custom, what software is responsible for creating the objects in the index in Azure? The way Kentico works is you create the index in Azure, then connect it via the keys. Next when you build the index in Kentico it creates the objects/fields in the Azure index. So I'm not 100% sure how a global event handler would NOT work if Kentico is in charge of defining that initial creation of the objects/fields in the index. If you have a 3rd party system pushing data to the index, the fields should be created and defined already so you simply push our data to it.

if Kentico doesn't support the newer library you need to use, then you need to work with Kentico to make that work or find another solution

Indeed, I've reached out to Kentico Support in the hopes that they will honor their 7-day fix guidance for this issue.

If the index is entirely custom, what software is responsible for creating the objects in the index in Azure?

Using a Kentico Scheduled Task that gets triggered when our product imports complete. That scheduled task makes a call to our custom document index class to kick off the bookkeeping for Azure Search.

Thanks for your replies @BrendenKehren - you helped me maybe answer my own question. I will try out the idea of having both Azure libraries installed side-by-side to see if that works. Will update this question as appropriate, based on the results of that.