View the original community article here
Last tested: Aug 31, 2020
First confirm that the Explore has been saved and then refresh the page to see if the explore is populating in the Explore dropdown.
If the explore still isn't showing in the Explore menu, check if:
extension: requiredparameter is defined in the Explore. An Explore with
extension: requiredis not visible to users on its own; it is intended only to act as a starting point to be extended by other Explores (documentation).
required_access_grantsparameter is used on the Explore. If this parameter is used and a user doesn't have the necessary corresponding user attribute values, they won't be able to see the Explore in the dropdown menu (documentation).
- If the Explore is extending an Explore, check whether the base/extended Explore has
There is also a known issue in which if there is more than one model with the same name, the explore menu will sometimes show the explores from the unconfigured model instead of the explores from the configured model, even though the links will take you to the explores from the configured model. Check the Manage Projects page to see if there is another model with the same name in a different project.