[BUG] Semantic configuration properties for prioritized keyword fields not accepting string subfields of type Collection(Edm.ComplextType) about azure-sdk-for-net

[github-actions]

@christothes @JonathanCrd

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[JonathanCrd]

This issue seems to be related to Azure.Search.Documents and not to Azure.Data.Tables.
I'm assigning it to the proper team.

[ShivangiReja]

Thanks for reaching out and we regret that you're experiencing difficulties. The Azure SDK packages do not have insight nor influence over an operation failure, they just surface the HTTP error returned by the Search service. As a result, this is not an issue that the Azure SDK team can assist with. You will need assistance from the Azure Search service team.

To ensure that the right team has visibility and can help, your best path forward for would be to open an Azure support request or inquire on the Microsoft Q&A site or Azure Search · Community.

CC: @mattgotteiner

[github-actions]

Hi @Debro012. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.