The process is:
Clone the existing topology
Add the components to the new Search Server
Activate the topology
More or less, it'll look something like this:
$si = Get-SPEnterpriseSearchServiceInstance -Local
$clone = $sa.ActiveTopology.Clone()
New-SPEnterpriseSearchAdminComponent -SearchTopology $clone -SearchServiceInstance $si
Use one of "unused Managed Properties" named Int00 - Int49.
Create a new Site Column in one of your Site Collections.
Add this column to a list or library and add at least one item to the list with data in the new column.
Wait for, or ...
We cannot export search configuration from central administration.
If you want to move the search service application from one environment to another environment, you could back up the search service application and restore it in another environment.
We can back up and restore search service application by PowerShell command or Central Administration.
This is because you're not actually creating a new field, you're simply updating the DisplayName property of the Title field. Since crawled/managed properties already exist for the Title field, no new properties are necessary and thus are not created.
Crawled/Managed Property Reference
That is just the way it is now with SharePoint online. If you click into one of the automatically created managed properties you'll see a banner at the top that says:
Automatically created managed property. Search automatically created
the CONTACTEMAILOWSTEXT managed property, but can't display the actual
automatic settings and mappings here. Instead it ...
First: There is not really much we can do to troubleshoot this issue since there are no logs to look into in SharePoint Online. Since the refiner works for SharePoint on-premise search results, I think you have done the configuration without error.
Second: It might take longer than you think for the custom refiner to take effect in SharePoint Online.
I found my answer by searching the internet.
Mentioned in the link below. It is necessary to pay attention to Url. And I typed the url wrong.
Site Level Schema - only view option is with this URL: /_layouts/15/listmanagedproperties.aspx?level=site
SiteCollection Level Schema - allows edit is with this URL: /_layouts/15/listmanagedproperties.aspx?level=...
I also had this issue due to a recent security update that the server team installed. It was actually a CU for SP2016 that impacted Search schemas. MS Support was assisting me in narrowing down the root cause. As an alternate to PSCONFIG, you can use the SharePoint 2016 Products Configuration Wizard to complete the CU deployment and ensure that the ...
We use SharePoint 2013 and we had it a few times that this did not work either. In our case resetting the index and performing a fresh full crawl solved our issue.
In case you try this and resetting the index throws an error you might want to take a look at this: Index reset throwing exception
ows_KBCategory = Text of the metadata field
ows_taxId_KBCategory = Unique ID of the metadata term
The ID property is used to get terms which are tagged or are a children of a term. So in your case the regular ows_KBCategory should be sufficient.
For more information check to following link an scroll to the part Data format for Managed Metadata:
AFAIK, in 2013 calculated columns were not automatically promoted. (This feature was removed in 2016 & SPO.) All you need to do, since you have central admin access, is create your own Managed Property for the field.