What you're doing is correct. You should be able to test this by running a report as yourself from an Explore built on the model that uses this connection. Then you can sudo as the other (i.e. the one with the "siem_2" database user attribute value) ...

In this case, it sounds like there may be an opportunity to reduce the amount of information on this single dashboard. Best practice for dashboard design leans toward simplicity. If users are having to do a lot of scrolling or are unable to find the ...

Yes, user attributes can be used to dynamically change the connection based on the user. However, it cannot be used in the "connection" parameter as you've attempted. Using liquid can only be used in LookML in the places noted in this link. To accomp...

The solution @lakshmi-1641424 didn’t work for me until I explicitly defined an [else_format] as documented here. Posting in case anyone gets stuck on this.