Can I put a single dimension from a view in its own dropdown on the value picker?

[jbernal]

We all know that adding a value_label parameter to a join puts the fields resulting from that join its own section or dropdown in the value picker. Can I do that to a single dimension from a view to separate it out into its own more noticeable section of the value picker?

Example:

• Orders view gets joined to an explore and all of the fields appear under a "Orders" dropdown on the value picker.
• EXCEPT the "Ordered By User" dimension (which comes from the same view) will appear in a separate dropdown called "Order By User" to help make it more visible and noticeable to report creators.

Is this possible?

[rallaking]

Hi! I also wanted to group some fields from one view separately from the other fields - mainly to ensure there was no confusion when scrolling through the list.

There isn't an option to separate the dimension out into a different value_label parameter, but there is another layer of labels you can use, which is group_label. This groups the fields at the same level as dimension groups (created_date, order_date, etc.) The group_labels can be added to the dimensions, measures, filters, parameters in the View and will group everything together by field type (dimensions together, measures together, filters together). If there is no group_label then the field (dimension, measure, etc) will show in alphabetical order with the group_labels.

Here is an example from Looker's webpage

https://cloud.google.com/looker/docs/reference/param-field-group-label?version=24.20&lookml=new 

It's now in our style guide to include the group_label for views using " x Details" (examples: Address Details, Product Details, Revenue Details) so it's standard to view a nested list of fields in the Explore. For the most important or frequently used fields, I'll create a group_label with a leading space so that it appears at the top of the listing (group_label: " Product Details").

[jbernal]

Thanks for the suggestion but we really want the fields to be in one of the main value picker dropdowns (like "Flights" in your screenshot) not the sub-dropdowns (ie. "Engine Details" in your screenshot). This makes them more noticeable and likely to stand out to the end user.

I think the only option that might work is rejoining the table to it self in the explore and giving it a different label. I've been hoping to avoid this so as to stay away from redundant code.