Azure AI Search - Import and vectorize data I can't I can't choose which fields I want to be filterable using Cosmos DB for NO SQL

@Alan José Vladimir Mendoza Navarro Thanks for posting your question in Microsoft Q&A, apologize for any inconvenience caused on this.

Could you please try updating the indexer fields using this Create or Update Rest API rather from Portal and let us know if you are still facing the issue.

Please do share if you are following any documentation to achieve your requirement.

Hi! @VenkateshDodda-MSFT ! Thank you very much for your answer. I will be reviewing what you gave me as an answer and see if I find a solution to what I am doing.

I would like explain my problem in more detail. What I was looking for was the way in which I can make these filterable field configurations from the Azure portal using "import and vectorize data", which did not let me configure directly, it appeared in the following way:

Then when creating all the objectives (index, indexer, ...) and when I went to the Search Explorer --> Fields section, I get the following image, which makes sense because when creating my index, I could not specify which fields had to be filterable, that is, my objective is that a field can be configured as filterable because I will need it for my project.

Now I was looking for a way in which I can filter after creating the index, and I found this first document: https://zcusa.951200.xyz/es-es/azure/search/search-filters where in the section "Make an existing field filterable" it mentions that you cannot modify an existing field to make it filterable and as an alternative it mentions that I should create a field or generate a new index but if I create the index again I think it would have the same result because it does not let me choose which fields I want to be filtered.

I also found another article https://zcusa.951200.xyz/es-es/azure/search/search-howto-reindex#updates-requiring-a-rebuild where it mentions that when changing the definition of a field such as the specific attributes (filterable) the ideal would be to delete the existing index and perform a rebuild.

It should be noted that I was looking for all this to find out why you cannot configure non-vector fields that are filterable using the "import and vectorize data" wizard.

I also tried the "import data" wizard where it gave me an option to vectorize a field.

However, it wasn't useful for the following reason: I understand that a vector field must have a Collection(Edm.Single) data type, so when I changed the data type of the documentType field, then when I made the necessary configurations and when I created the index, it wouldn't let me and I got the following problem.

Which makes sense because in my database the documentType is defined as a String, so if I wanted to change the data type to Collection(Edm.Single) the latter should have a vector value stored in my original database; which is different from "import and vectorize data" because the latter before configuring your fields asks you which field you want to vectorize and based on that it autogenerates a vector field and also keeps the field with which you have vectorized so it does not lose information.

Well, I know it is very long but these are some problems that I have had because I cannot find the option of how to filter my fields when I use "import and vectorize data". I mean, all I do is to not put too much hand in the code because I am doing a POC and I am using Azure AI Search.

Any observation or response would be very grateful, thank you very much.

Alan Mendoza.

Hi! @VenkateshDodda-MSFT

I found another article https://zcusa.951200.xyz/es-es/rest/api/searchservice/update-index where it mentions that an index can only be updated taking into account the following scenarios:

Which I identified with it that the index attribute change could not be made so that a field that has been created as non-filterable is filterable later.

If you have any observations, please let me know. Thank you!

@Alan José Vladimir Mendoza Navarro Thanks for sharing more details and apologize for the delay in my response.

As I understand that you want to make the changes to an existing field in the index to make is as searchable to do that as mentioned in the documentation you need to delete and rebuild the index.

only the below operations mentioned below can be done without rebuilding the index.

Hi! @VenkateshDodda-MSFT thanks for your reply.

Sorry if I didn't make myself clear what I needed.

My main objective is that an existing field in the index is filterable, it would really help me a lot if there is a solution for this using the wizard, otherwise my last option would be to create code with python.

Thank you very much c: