This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Here’s where you’ll find a buzzing community of Security professionals from around the world with one common mission: bringing their Security platforms to the next level.
Knowledge DropLast tested: Apr 1, 2020 There are several variations to
this error, but one common one is when a user extends viewA in viewB,
then extends both viewA and viewB in viewC. In this case, the extends
logic seems to conflict. They shouldn't...
Knowledge DropLast tested: May 15, 2020 IN SOME SITUATIONS:You can use
&origin=drill-menu at the end of your link: parameter to force it to
open in a drill modal in the current tab rather than a new window. There
are certain known situations where th...
Knowledge DropLast tested: Oct 19, 2020 WHAT DOES THIS MEAN?We most
commonly see this response when an API consumer is incorrectly using the
origin header in an API call.CORS is only available when using the new
experimental API 4.0. As such, any req...
Knowledge DropLast tested; Feb 4, 2020SAML user mappings are updated
when the user logs in. Have the user log out and log back in to reflect
the change.This content is subject to limited support.
Knowledge DropLast tested: 8/26/2022Note: This content is also available
on Github. Are you lazy like me and want to avoid having to refresh your
auth token periodically when using the Looker API in Postman? This guide
will help you to configure your...
When you use a parameter with type: string, the
parameter_name._parameter_value Liquid variable requires that you
enclose the values of the parameter with both single and double quotes.
This is so that the single quotes are transmitted to the SQL,
id...
If you want to use a cross join, you’ll either want to use `sql_on:
1=1;` (note this is `sql_on`, not `sql`) or simply leave the sql/sql_on
field
out.https://docs.looker.com/reference/explore-params/type-for-join#examples
Hi @graydon! Thanks for letting us know about this. It looks like we do
have this filed with our engineering team, and they are targeting the
next release (7.14) for a fix for this issue. Keep your eyes peeled for
that fix in the change log.
https://...