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 are also 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)
Business users report that they are unable to build useful queries because the list of fields in the Explore is too long to find what they need.
Which three LookML options should a developer use to curate the business user's experience? (Choose three.)
A user reports that a query run against the orders Explore takes a long time to run. The query includes only fields from the users view. Data for both views is updated in real time. The developer runs the following query in SQL Runner and quickly receives results:
SELECT * FROM users.
What should the developer do to improve the performance of the query in the Explore?
A developer has User Specific Time Zones enabled for a Looker instance, but wants to ensure that queries run in Looker are as performant as they can be. The developer wants to add a datatype: date parameter to all dimension_group definitions without time data in a table-based view, so that time conversions don't occur for these fields.
How can the developer determine to which fields this parameter should be applied through SQL Runner?
A LookML developer creates a new model and a test dashboard from the model. The developer shares the link to the new dashboard with users, but the users report that all they see is the ''Model Not Found'' error.
What is a possible cause of this issue?
