Project Well Header Table for "company level" wells is empty

Guidance
1

Hello,

I tried pulling the wells table for one of my projects and the table was empty. I created this project with one well that was coming from our “company” level. I then deleted the well and imported the well data directly into the project through the data import and in this case the well header table populated. How can I download wells table for a specific project that are comprise of wells whose information is kept at the company level?

2

Hey Eduardo, can you please clarify this bit.

What endpoint are you using to retrieve the data? Is v1/projects/:projectId/company-wells endpoint what you are looking for?

3

If I add wells from the company level to a specific project and then try to pull the well header information with:

projects/:project_id:/wells

they don’t show up. It sounds like I should be using the company-wells endpoint but then my next question is what happens if there is a combination of company level and project level information for the same well. Which one takes precedence? If I want all the wells for a specific project should I be hitting both endpoints (wells/company wells)?

4

If you update any of the company level wells in a project it will update the company level wells and you should see the changes. As such, there is no distinction between company and project level information for a well.

If you have a mixture of company and project level wells then yes.

5

Thank you! I’ll hit both endpoints

6

What @HGantz says is correct. But just to expand a bit more on the first point, if you add a company well to a project, that well that you’re seeing is still in the company level, and any information that you can see or edit for it is shared between all projects using that well. If later you import the same well to the project scope by doing a project scoped data import, then you will see them as different wells. Even if they have the same data source and chosen id, they will appear as two separate wells in CC, because they have different scope (one is scoped to company, the other to the project). When you use the API, you can get one of them by using the v1/projects/:projectId/company-wells endpoint and the other by using v1/projects/:projectId/wells. So yeah, company and project well information is never mixed together.