JSON parser does its best and as there are no trailing .0(no decimal point) it interprets that as long, leading later to InvalidCastException as casting object{long} to decimal fails
So why did Episerver Find omit .0, seems to be only happening for dev indexes and not production ones
Are we doing something wrong in multiple projects or is this Episerver Find issue?
Lately and seems only in development indexes we get following exception:
Property in question is defined as follows:
Mostly it contains price that has only 0 after decimal point, for example 189 and not 189.01
So when 'EPiServer Find Content Indexing Job' is ran following can be observed, in Fiddler, for example:
Note that it has: .0
When this very same object is retrieved from Episerver Find, its sent back as:
So what happens next is JSON deserializer treats this field now as long and not as double or decimal
Leading to this:
full image
JSON parser does its best and as there are no trailing .0(no decimal point) it interprets that as long, leading later to InvalidCastException as casting object{long} to decimal fails
So why did Episerver Find omit .0, seems to be only happening for dev indexes and not production ones
Are we doing something wrong in multiple projects or is this Episerver Find issue?
Find version 12.3.1 or 12.4.0