Correct, unfortunately creating a string field in Table Calculation has its downsides. You’re creating a new field which means no formatting is applied because of the order of execution of different aspects of the data.
You could also create this field in LookML (though it would be duplicated). You wouldn’t concat this field in SQL just use first field in SQL but then use {{ second_field._value}} in the html parameter. I recall some ways to apply at least the thousand delimiter in there.
It would be something close to this:
measure: first_field {
type: sum
sql: ${TABLE}.first_field ;;
html: {{ rendered_value }} out of {{ second_field._rendered_value }} ;;
value_format_name: usd
}
dimension: second_field {
type: sum
sql: ${TABLE}.second_field ;;
value_format_name: usd
}
By using {{ rendered_field }}, you’re telling Looker to use the output of the rendering process of each field before combining everything into the output of HTML parameter.
LinkedIn
Twitter
