Is there a way to map managed taxonomy crawled property to an out of the box RefinableString managed property through code?

[kstat]

@wobba - Thanks for sharing this script and for your blog posting here.

I have a use-case where I need to map approximately 90 crawled properties to a single Search managed property at a tenant-level in SP2013 and SPO. I've checked the published Search Limits and it looks like it caps out at 100 crawled properties that can be mapped to a single managed property (besides other limits which I anticipate to be well within). Presently, the key challenge appears to be manual nature of the task at hand and the tedious and slow UX process and multiple clicks required to map all these taxonomy crawled properties to managed properties.

Are you aware of an automated way to do this mapping through script / code? In case not, and if we do the mapping once in SP2013, could an export and import of the search configuration from on-premises work as expected to SPO or will the mapping need to be re-applied in SPO manually?

[wobba]

You should be able to use https://github.com/wobba/SearchConfiguration/blob/master/MapCrawledPropertyToManagedProperty.ps1 for each cp. Could be more efficient to bundle it, but should solve your case.

[kstat]

Thanks @wobba. I had come across this script as well, but it looks like we're writing out a warning and returning from the script if the crawled property being mapped is an 'ows_taxId*' property. Are we saying this script may still work if we remove that failsafe check in the code?

[wobba]

Good question as I don't quite remember why I added this check. You can do a manual mapping of one yourself in the UX. Then export the search config and examine the XML.