We’re excited to share that we are rolling out a series of enhancements that will improve your experience with Matik’s Looker integration and help your Looker-powered dynamic content perform better. Please review your content by Feb 1st, 2025 to ensure a seamless experience.
What’s Changing
We’re updating how Looker connects to dynamic content in Matik. This includes the following enhanced functionality:
- Improved Query Logic: Dynamic content will no longer save a static version of Looker queries. Instead, it will save the query setup and fetch fresh data each time it's used.
- Hidden Fields Visibility: Hidden fields from Looker will now be shown within Matik, clearly marked as hidden. You can hide or unhide these fields directly within Matik.
- Error Validation in UI: Any mismatches with Looker will be flagged within Matik, helping you quickly identify and resolve issues on the Looker side.
Impact on Your Workflows
As part of this update, any inputs or dynamic content connected to Looker will display red error text within Matik to highlight mismatches that need to be resolved.
For now, the dynamic content will continue functioning as it has been, using the current method of retrieving data. Once you click "UPDATE," the content will switch to the new data retrieval process, and all newly created content will automatically use the updated process as well. Double-check that your content is functioning as expected before updating, as this step cannot be undone.
What You Need to Do
- Review all dynamic content connected to Looker. Any mismatches will display as error messages that can be resolved in Looker.
- Use the "Test API" feature to confirm that the dynamic content returns the expected results.
- Once the content is error-free and working as expected, click "UPDATE" to finalize. Only proceed when you're certain, as any changes—even minor edits—will apply the new data retrieval process.
Resolving Common Issues with Looker
Below is a list of potential errors you may encounter, along with the steps to resolve each issue and ensure your dynamic content is functioning correctly.
| Error Message | Why it Happens | How to Resolve |
| Dashboard cannot be found | Occurs if the dashboard was deleted. | Restore the deleted dashboard; the error message will specify the dashboard ID in Looker. Otherwise, you can recreate the dashboard. |
| Dashboard query cannot be found | Occurs if the dashboard query was deleted. | Recreate the deleted query, or select a new query. |
| Field cannot be found | Occurs if the field was deleted or renamed. This can apply the fields to return and/or to fields used to filter, sort, or pivot. |
If the field was renamed, update its name in Looker to match what’s in Matik or remove the old field in Matik and re-add the updated field. If the field was deleted, you can recreate it. |
| Table calculation field is missing dependencies | Occurs if a calculated field is added, but its dependent fields are not. | Add the dependent fields; the Matik error message will specify the missing fields. |
This video provides step-by-step guidance on troubleshooting issues that might arise with your looker instance.
Comments
0 comments
Please sign in to leave a comment.