[BUG] Request connector JSON converter: tsField only works at first level

[albham]

Connector name (If bug in the some connector):
REQUEST Connector

Describe the bug
When the tsField expression points to a field in the first level of the JSON the time value is correctly read, however when it refers to a second level field, its value is not taken into account.

Steps to Reproduce
If my API returns

{
  "device": "pruReq1",
  "D1234": {
    "temperatura": 20.1,
    "pw": 33.5
  },
  "fecha": "2025-10-20T11:49:46.481Z",
  "estado": "OK"
}

The date is read correctly as data timestamp if I use the configuration

        "telemetry": [
          {
            "key": "temp",
            "type": "float",
            "value": "${D1234.temperatura}",
            "tsField": "${fecha}"
          },

on the other hand, if my API returns

{
  "device": "pruReq1",
  "D1234": {
    "temperatura": 20.200000000000003,
    "pw": 33.5,
    "fecha": "2025-10-20T11:53:37.637Z"
  },
  "estado": "OK"
}

and with the configuration

        "telemetry": [
          {
            "key": "temp",
            "type": "float",
            "value": "${D1234.temperatura}",
            "tsField": "${D1234.fecha}"
          },

timestamp corresponds to the time of access and not the date shown in the tsField field

Versions (please complete the following information):

• OS: Ubuntu 24.04
• Thingsboard IoT Gateway version: Docker last release (3.7.8)

[samson0v]

Hi @albham, thanks for your interest in ThingsBoard IoT Gateway!
We will fix this behaviour in the Gateway v.3.8.0.
So, let's stay connected!