Not sure if anyone else has experienced this yet, I just noticed in the latest release (2023.2.11) that if you send a data view to a function, and your data view contains columns that are decimal, these decimals are now converted to integers by the time the data view reaches the function.
In dev tools network tab you can see the request still has the decimals; when the data view is being parsed into a data table the decimals are lost.
So it looks like how Epicor is converting the request param to a datatable is by using JsonConvert.Deserialize, which there is a known limitation about it removing decimals related to the DataTableConverter used in json.net. I am pretty sure this worked in the past, meaning Epicor was handling this limitation when converting json request param to datatable.
The real problem is that the data view does not honor the decimal formatting that you define on the data view columns, which would then make the above issue a seemingly non issue?
