Embedded Business Intelligence Software Resources

Hey Carlos! I'm Izzy, the Looker Community manager. Yeah, especially in huge SQL queries it can be hard to figure out exactly where the issue lies. That error that pops up on explores doesn't help, since like you said, you don't know where that position is. If you open the offending query in SQL runner (Via the SQL tab near the results) and run it there, when it fails you will be able to scroll through the query and find the issue highlighted with a red X on the side of the window. It's not ALWAYS the exact place you need to fix something, but it's usually close and can be extremely helpful. In the future, you can also post questions like this on the Looker Community forums— https://www.discourse.looker.com, it's full of other Looker users and more lively than the G2 comment section.

Hey Brian! I'm Izzy, the Looker Community manager. There's 2 components here (well, a few more, but 2 high-level ones). Folder/content access and data/query access. For content access, we recommend you turn on the "Closed System" when working with a multi-tenant setup ( https://docs.looker.com/admin-options/tutorials/access-controls#configuring_a_closed_system ). By default, that entirely isolates users from different groups/brands from one another— And it's controlled by Looker groups so you can attach it to the actual model/data permissions. There's a whole slew of ways to do data security. You can extend explores, rather than entirely rebuilding them, and/or use access_grants (https://docs.looker.com/reference/model-params/access_grant) or even sql_always_where and user attributes, to limit access to data. There's a bunch more options, so I might repost this question on our community forums at www.discourse.looker.com. They're more lively than the G2 comment section and you might get some interesting examples from customers.

Create averages in the query and use the results in the charts