One of our clients set up an explore in their instance. It looks like they created it in some really non-standard way because no one can access the underlying view/model files, yet we can still access the explore itself.
Any idea why this would happen?
There is only one project in this looker instance. Looking at the URL for the explore in question, the project name is prefixed with a t__
, which only seems to happen with this particular explore ... not sure if that is a useful clue or not.
I have sudo’d as the user who created the explore, but I’m still not able to access the underlying view/model files.
Solved! Go to Solution.
Found out what it was … it had the t__
and wasn’t associated with any lookML files because it was an explore generated directly from a SQL Runner query
Found out what it was … it had the t__
and wasn’t associated with any lookML files because it was an explore generated directly from a SQL Runner query