Override datatype doenst work with TX Enhanced Drivers

Hi,

you might want to set the culture settings to either en-us or your local region and see if that changes anything. You can also turn on two useful features to help track down issues:

• debug logging: will generate a central logfile that contains the calls and dynamic values amongst other things
• caching: by default the connectors work in-memory, but you can specify a folder to log to, this will create raw (response from the API), XML (conversion of raw to xml) and transformed (conversion of XML through table builder)

It is probably good to check if the raw response from the API looks strange.

Turning on Culture didn’t help.

The issue is that I am unable to override the datatype for that column. The value it receives is Text, while datasouce is expects it to be Int.

This works fine with CData because I can override the values both on Data source and RSD-file. 

Hi,

have you already turned on exhaustive metadata scanning in the endpoint? It should parse all the data and determine field types based on that instead of on the first few records.

​@aftabp are you still experiencing this issue? Did you try turning on the exhaustive metadata scanning as suggested by Rory?

​@Christian Hauggaard sorry for the late reply. 
I havnet worked with TX for a while, but will resume work soon.

​@Christian Hauggaard 
I have tried it again. 
I havent treid ​@rory.smith’s suggestion because the the source has huge ammounts of data.
The workaround was to delete the endpoint and recreate it
So, i deleted the endpoint where i useed this JSON:

[
    {
        "id": 12345,
        "name": "Aftab"
}
]

and used this instead:
 

[
    {
        "id": 1A2345B,
        "name": "John"
}
]

/*/

exhaustive metadata scanning in the endpoint helped

I have open a case about this after discovering that it did help after all,