Bradley Turner

Same here! only I am on dotnet 3.1 and odata 8.0.1. Using [EnableQuery] and EdmModel at startup

Yeah you're right thank you, setting the field type to string lets the user enter numbers correctly so that isn't an issue. However when you have a type string for...

The preview when you go to filter/transform the data is correct though it is just those value boxes in the view that I think could confuse someone because a valid...

Going into code mode fixes this issue but I really don't want a user to be editing json without a nice UI like tree mode. I am just hoping tree...

This basically boils down to an option that would be: (options = {explicit_strings: false;}) input/display your strings like this in tree mode: asdf