Looker Connect Training

Help Center

Documentation

Community

Cloud Certifications

Solved

BigQuery dimension group datetime datatype time timeframe issues

  • 18 November 2021
  • 6 replies
  • 125 views
R

We have a datetime dimension being read from BigQuery, the problem is on Looker it converts the time value to Zeros.

Is there anyone to retain the time value?

 

  dimension_group: placed_at_local {
    type: time
    datatype: date
    timeframes: [
      raw,
      hour,
      time,
      date,
    ]
    sql: ${TABLE}.placed_at_local ;;
  }

 

icon

Best answer by Raghad Awwad 29 November 2021, 10:14

View original
This topic has been closed for comments

6 replies

Kehinde

Try and cast the value to a TIMESTAMP @Raghad Awwad 

Regards, Kehinde.
Kehinde

try this and let me know if it works. Mark as helpful if it does. @Raghad Awwad 

  dimension_group: placed_at_local {
    type: time
    datatype: date
    timeframes: [
      raw,
      hour,
      time,
      date,
    ]
    sql: CAST(${TABLE}.placed_at_local AS TIMESTAMP) ;;
  }

 

Regards, Kehinde.
R

Unfortunately @Kehinde, it didn’t work. It produced that same error that forced me to define the dimension as a datatime.

 

 

Kehinde 
  dimension_group: placed_at_local {
    type: time
    datatype: datetime
    timeframes: [
      raw,
      hour,
      time,
      date,
    ]
    sql: CAST(${TABLE}.placed_at_local AS TIMESTAMP) ;;
  }

or 

  dimension_group: placed_at_local {
    type: time
    datatype: timestamp
    timeframes: [
      raw,
      hour,
      time,
      date,
    ]
    sql: CAST(${TABLE}.placed_at_local AS TIMESTAMP) ;;
  }

or

  dimension_group: placed_at_local {
    type: time
    timeframes: [
      raw,
      hour,
      time,
      date,
    ]
    sql: CAST(${TABLE}.placed_at_local AS TIMESTAMP) ;;
  }

I see, you are have a data type mismatch, comparing datetime and date. try the above. (The second third preferably) let me know how it goes. @Raghad Awwad 

Regards, Kehinde.
R

Thank you @Kehinde , the first suggestion worked for me. My mistake was using

datatype: date

which ignored the timestamp

datatype: datetime

corrected that.

Kehinde

Please mark as helpful. I am happy to help and will always help. @Raghad Awwad.

Regards, Kehinde.
Terms & Conditions