Ooh, good point. A parameter can only take one value.
I tried using a LookML filter field instead, since those can take any number of values, but those can’t be referenced in the sql parameter like we need.
What about defining the permutations that your users are likely to choose?
parameter: manage_columns_filter {
type: string
default_value: "DateOfBirth"
suggestions: [ "DateOfBirth", "DateOfBirth and Age", "DateOfBirth and Salary", "Age", "Age and Salary", "Salary", "DateOfBirth and Age and Salary"]
}
