How to fix "The data field _ in the document with key _ has an invalid value type of Edm.Double. The expected type was Edm.Int32

Question

How to fix "The data field _ in the document with key _ has an invalid value type of Edm.Double. The expected type was Edm.Int32

Tyler Suard 155

Hello. I have set up a data source and an indexer. Everything was working fine until this morning, now I am getting the above error message. My data source is cosmosdb, and it takes a string and converts it into a number using StringToNumber. Apparently StringToNumber converts it into a Double, but my index can only take an Int32 in that field. How do I make StringToNumber return an int32?

Laxman Reddy Revuri 5,405 Reputation points Microsoft External Staff Moderator

2024-12-03T08:17:04.92+00:00

Hi @Tyler Suard
Thanks for the question and using MS Q&A platform.
Azure AI Search doesn’t provide a direct way to return an Int32 using the StringToNumber function, but it chooses the most suitable numeric type based on the data. To ensure you get a 32-bit integer (Int32).
When creating your index, define the field type as Edm.Int32 in the schema.

Make sure your values fall within the Int32 range (-2,147,483,648 to 2,147,483,647).

The StringToNumber function converts a string into a number. If the number fits within the Int32 range, it’s usually treated as a 32-bit integer. However, if the value is too large, it may be treated as a 64-bit integer (Int64) or a double-precision number (Double).

The field type defined in the schema (e.g., Edm.Int32 or Edm.Int64) determines how numeric fields are handled in queries. To work specifically with Int32, always set the field type as Edm.Int32 in the index.
I hope this information is helpful.
If the answer is helpful, please click "Accept Answer" and kindly upvote it.
Laxman Reddy Revuri 5,405 Reputation points Microsoft External Staff Moderator

2024-12-04T08:53:06.6+00:00

Hi @Tyler Suard
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Tyler Suard 155 Reputation points

2024-12-04T17:27:05.5766667+00:00

I solved this issue. The problem is, that particular field was coming in as a string from CosmosDB, and it was "0.0". When I used "StringToNumber(field))" in my data source, it was interpreting 0.0 as a double-precision float. I just changed the data source to use ROUND(StringToNumber(field)) instead. That rounded the number up to 0 instead of 0.0, which was interpreted as a 32bit integer rather than a double.
Tyler Suard 155 Reputation points

2024-12-04T17:27:24.7533333+00:00

I solved this issue. The problem is, that particular field was coming in as a string from CosmosDB, and it was "0.0". When I used "StringToNumber(field))" in my data source, it was interpreting 0.0 as a double-precision float. I just changed the data source to use ROUND(StringToNumber(field)) instead. That rounded the number up to 0 instead of 0.0, which was interpreted as a 32bit integer rather than a double.

Accepted answer

0 additional answers

Your answer

Laxman Reddy Revuri 5,405 Reputation points Microsoft External Staff Moderator

2024-12-03T08:17:04.92+00:00

Hi @Tyler Suard
Thanks for the question and using MS Q&A platform.
Azure AI Search doesn’t provide a direct way to return an Int32 using the StringToNumber function, but it chooses the most suitable numeric type based on the data. To ensure you get a 32-bit integer (Int32).
When creating your index, define the field type as Edm.Int32 in the schema.

Make sure your values fall within the Int32 range (-2,147,483,648 to 2,147,483,647).

The StringToNumber function converts a string into a number. If the number fits within the Int32 range, it’s usually treated as a 32-bit integer. However, if the value is too large, it may be treated as a 64-bit integer (Int64) or a double-precision number (Double).

The field type defined in the schema (e.g., Edm.Int32 or Edm.Int64) determines how numeric fields are handled in queries. To work specifically with Int32, always set the field type as Edm.Int32 in the index.
I hope this information is helpful.
If the answer is helpful, please click "Accept Answer" and kindly upvote it.
Laxman Reddy Revuri 5,405 Reputation points Microsoft External Staff Moderator

2024-12-04T08:53:06.6+00:00

Hi @Tyler Suard
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Tyler Suard 155 Reputation points

2024-12-04T17:27:05.5766667+00:00

I solved this issue. The problem is, that particular field was coming in as a string from CosmosDB, and it was "0.0". When I used "StringToNumber(field))" in my data source, it was interpreting 0.0 as a double-precision float. I just changed the data source to use ROUND(StringToNumber(field)) instead. That rounded the number up to 0 instead of 0.0, which was interpreted as a 32bit integer rather than a double.
Tyler Suard 155 Reputation points

2024-12-04T17:27:24.7533333+00:00

I solved this issue. The problem is, that particular field was coming in as a string from CosmosDB, and it was "0.0". When I used "StringToNumber(field))" in my data source, it was interpreting 0.0 as a double-precision float. I just changed the data source to use ROUND(StringToNumber(field)) instead. That rounded the number up to 0 instead of 0.0, which was interpreted as a 32bit integer rather than a double.

Answer 1

Hi @Tyler Suard
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.

Ask: How to fix "The data field ___ in the document with key ___ has an invalid value type of Edm.Double. The expected type was Edm.Int32

Solution:I solved this issue. The problem is, that particular field was coming in as a string from CosmosDB, and it was "0.0". When I used "StringToNumber(field))" in my data source, it was interpreting 0.0 as a double-precision float. I just changed the data source to use ROUND(StringToNumber(field)) instead. That rounded the number up to 0 instead of 0.0, which was interpreted as a 32bit integer rather than a double.

Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

Share via

How to fix "The data field ___ in the document with key ___ has an invalid value type of Edm.Double. The expected type was Edm.Int32

0 additional answers