Q1

Axn
New Member

A LookML developer adds an access_filter parameter to an Explore. When using the Explore, the developer notices that there is no WHERE clause in the generated SQL. The developer sudos as a business user to test the filter and sees the WHERE clause in the generated SQL filtering on the user attribute value as expected.

What is the reason for the missing WHERE clause when the developer uses the Explore?

A
There is a LookML error regarding the access_filter parameter, so it isn't being applied to the Explore.
B
The developer added a default_value: "" parameter to the access_filter parameter.
C
The developer's user attribute value is %, NULL.
D
The developer's user attribute value is blank.

0 0 70
0 REPLIES 0
Top Labels in this Space
Top Solution Authors