Autoowstaxidmetadataalltagsinfo doesn't create AutoRefinableString since upgrading from v4.5.2 to 4.7

[ileana2019]

Version used Ex: 4.7

We upgraded the app from v4.5.2 to 4.7 and we are using Managed Metadata SharePoint columns linked to RefinableStrings managed properties. When using the v4.5.2, we could setup the Search Results webpart to enable localization and use the Autoowstaxidmetadataalltagsinfo for the Tags layout slot. Then in the Manged Columns, we could add AutoRefinableString to the details lists. With the same settings, in v4.7, the AutoRefinableString are not created anymore (in order to nicely display the managed metadata fields).

To Reproduce Steps to reproduce the behavior:

1. On the search results webpart properties: Enable localization to On and, in Layouts slots, link the Tags to the Autoowstaxidmetadataalltagsinfo
2. Select Details list as layout
3. Click on Manage columns
4. In the Select property drop down list, the AutoRefinableString is not created

Expected behavior The AutoRefinableStrings should be created automatically, when setting up the webpart as described above.

[ileana2019]

Maybe this issue and the issue: https://github.com/microsoft-search/pnp-modern-search/issues/2212 are somehow linked?

[ileana2019]

I will add 2 screenshots for this issue: The first one is a search page where we added the v4.5.2 of the pnp and then we migrated to v4.7: The second one is a search page where we added the v4.7 of the pnp: Both have the same pnp settings.

[FranckyC]

Hi @ileana2019, FYI the "Autoowstaxidmetadataalltagsinfo" property (and all 'AutoXXX' properties in general) has nothing to do with filters actually. It is only useful to be used in results display. In filters configuration you use "owstaxidmetadataalltagsinfo" property only.

Also, for the 'AutoXXX' proeprties to be created and selectable in the dropdown list (from layouts for instance), you must have results containing values for the original property. If don't don't see anything, this is probably there are no such results. In this case, instead of selecting the property, you can simply type the proeprty name manually and press 'enter' to validate the setting.

Anyway, can you confirm this works with 4.5.2 but not with 4.7.0 with the same data? Also, dumb question I know, but did you check the term actually exist in the term store with these IDs?

[ileana2019]

Hi @FranckyC , I Started again from scratch, to recreate the search page, where I added just the Search results webpart and the Filters webpart. In the search results I see the following result (Enable Localization is On) :

In the filters webpart I do not see any results; The filters webpart is configured as following:

The RefinableString is configured as following:

So how do I nicely display the RefinableString (linked to a Managed Metadata column) in the search results (just the text, without the IDs)? And why I do not see any results in the filters? This used to nicely work in v4.5.2 (by setting the Enable Localization to On in the search results webpart, and by linking the slot name "Tags" to the slot field "Autoowstaxidmetadataalltagsinfo".

[FranckyC]

@ileana2019 did you connect filters WP and search results WP both ways? With the localization flag 'on' you should use AutoRefinableString110 field in your "Cluster" column to display the friendly label (or map that field to the 'Tags' slot)

[ileana2019]

Hi @FranckyC, Indeed, I forgot to connect the search results webpart to the filters webpart. Thank you for pointing that out! I now see results in the Cluster filter, but it says "Term with ID not found": I tried to map the slot Tags with RefinableString110 and Autoowstaxidmetadataalltagsinfo, still no change. I cannot see the AutoRefinableString110 in Manage columns:

[ileana2019]

Hello, Are there any updates to fix this bug? @FranckyC could you please remove the label Needs Author feedback? Because I did give the feedback. Thank you!

[VerlindenEAM]

Hello @FranckyC and @wobba , Could this be related to discussion 2403 ?

[wobba]

@VerlindenEAM don't think so as #2403 is about merged terms. But I see the output looks the same,

[kasperbolarsen]

@ileana2019 Can you verify if this issue exists in the current version?