A developer needs to add an Explore built off of the orders view, which surfaces only completed orders. An orders Explore exists that contains all order information. Fields from the orders view arealso referenced in other existing views such as ${orders.fieldname}.
How should developer define a new Explore for completed orders and keep all field references working correctly?
A)
B)
C)
D)
A developer commits changes after adding LookML for a new measure. Upon pulling from production, the developer notices the following lines in the LookML:
A developer would like to add a new dimension of type: yesno for the enabled column in their users table. The column is of type: string in the database and returns yes and no values.
How should the developer define the yesno dimension?
A)
B)
C)
D)
A LookML developer has written the following persistent derived table. It references orders_rollup, another persistent derived table that also rebuilds with the same SQL trigger value.
Which change is needed to guarantee that user_facts will always rebuild with the latest data from orders_rollup?
A user reports that, when a date dimension is filtered to “before now” results are returned that consistently include tomorrow. Dimension fill has been ruled out as a cause of the issue.
Which LookML parameter should be used to resolve this issue?
