View the original community article here
Last Tested: Mar 5, 2021
No, you can use hidden only at the explore and field level (documentation).
BUT, there are workarounds.
Method 1: use fields: [] instead on the join (documentation). This will effectively do the same thing as hidden would because it tells Looker to not bring any fields into the explore. Caveat: If any current content uses fields from this join, the content will break because the fields are no longer in the explore.
For example:
join: foo {fields: []}
Method 2 (better way): use an empty view_label parameter in the join (documentation).
For example:
explore: orders {
join: users {
type: left_outer
sql_on: ${orders.user_id} = ${users.id} ;;
relationship: many_to_one
view_label: ""
}
}
Will show up as this in the explore:
This content is subject to limited support.