The process of building custom solutions for SharePoint Server.
Based on your description, I understand that you have a main SharePoint site where search refiners and RefinableStrings are working perfectly, but on one of its subsites, these same RefinableStrings are not appearing or returning any refinement values.
Before I dive into troubleshooting, could you please let me know if these RefinableStrings were previously working on this subsite, or is this a brand-new subsite where they have never appeared? Knowing this will help me isolate whether we are dealing with a propagation delay, a configuration block, or a synchronization break.
In SharePoint Server, refinable strings depend on the Search Schema mapping, crawl status, and Refinement Web Part configuration. Please first verify that the crawled property is mapped to a built-in refinable managed property such as RefinableString00 through RefinableString99. When creating the mapping, make sure you select the crawled property with the ows_ prefix rather than the ows_q_... version.
After the mapping is configured, reindex the affected list or library and run a crawl from the Search Service Application so that the new values are added to the search index.
Also check the search results page in the subsite and ensure that the Refinement Web Part is configured to include the same RefinableStringXX property used on the main site. Custom refiners must be explicitly added to the Refinement Web Part before they will appear on the search results page.
Finally, compare the result source, query transform, and any path filters between the main site and the subsite. Refiners only appear when the current result set contains values for the associated managed property.
If possible, could you please provide a bit more detail about the issue? That will help me better understand the scenario and assist you more effectively.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.