Why are explores getting auto created in my model?

[ginandtobby]

Hi Community!

I have a View A defined in a view.lkml file, and I have defined an Explore A using View A in a model.lkml file under Model A. Then, I defined some explores in another model, Model B, in which I included some view folders that contain View A.

Then, something strange happened: I did not explicitly define Explore A in Model B, yet Explore A is now available in Model B. So, if I search for Explore A in the search bar, there will be two search results—one for Explore A under Model A and another for Explore A under Model B. If I check the LookML link for Explore A under Model B, it points to the Explore A defined in the model.lkml file under Model A.

Could someone please advise why this has happened? Is it true that when a view is included in a model, an explore for it is automatically created?

Thanks!

[schoolsofthough · Accepted solution]

You said you included Model B Explores in view files? If so, and you included those view files in Model A then that is the same thing as including Model B Explores in Model A. 

It'd be a little easier if you could share some LookML code 

[blue1]

Check if include: "model_a.model" is in model_b.model.
If so, remove that include.

But I agree with @schoolsofthough that LookML code would help in this case.