Pushing custom fields to ComboCurve

Documentation
1

Problem:
You may have attributes that are specific to your organization that you may want to have available in ComboCurve.

Solution:
ComboCurve supports custom well headers, and they can be pushed using the REST API.

The following data types are supported for custom fields:

  • Boolean
  • Date
  • Number
  • String

The field names for the custom fields are static when sending data back and forth through the API, as shown below, but the field names shown in the ComboCurve app can be customized in the Company > Custom Columns page.

Here’s a full list of custom fields:

customBool0
customBool1
customBool2
customBool3
customBool4
customDate0
customDate1
customDate2
customDate3
customDate4
customDate5
customDate6
customDate7
customDate8
customDate9
customNumber0
customNumber1
customNumber10
customNumber11
customNumber12
customNumber13
customNumber14
customNumber15
customNumber16
customNumber17
customNumber18
customNumber19
customNumber2
customNumber3
customNumber4
customNumber5
customNumber6
customNumber7
customNumber8
customNumber9
customString0
customString1
customString10
customString11
customString12
customString13
customString14
customString15
customString16
customString17
customString18
customString19
customString2
customString3
customString4
customString5
customString6
customString7
customString8
customString9

Documentation:

1 Like
2

This is helpful Maikel. So it appears there are no material differences between the full array of header fields when connecting via API and those currently within the project-level Combo Curve platform. Is that fair?

1 Like
3

Yes, the custom fields in the REST API refer to the same custom fields in the ComboCurve UI. The UI additionally allows to control which what is used across the app, for example you can set customString0 to something like Interest Type , but this is a display name only and does not affect the fields synced through the API.

4

Very helpful, thanks Maikel!

1 Like
5

@maikel.ruiz thanks for this page - creating a customString header to denote region and was wondering if I could edit the field instead of just in the UI

1 Like
6

@michael.tanner so to confirm, you would like to edit the display name (e.g. Region) through REST API directly and not having to do it manually through the UI?

If that’s the case, that’s not currently available, but we can track it as a feature request.

7

@maikel.ruiz not exactly (though that would be cool!) - I created a custom text header in the UI and named it “Client” but when I GET wells, its returns the name as “customStringetc” and then the correct region value - no biggie just need to track any custom headers I create

8

Yeah, that’s the expected. The actual field names can not be changed, only the display value in the UI.

1 Like
9

Does this function work for the customString fields? We track our geology tops (i.e. which zone is each well in according to our geologists?) in a custom string field when we import them into the company level database. However, every time we Push header data into Combo Curve, the customString field seems to be deleted. Will this be updated to include customStrings?

10

@Mark_Hinaman,

How are you importing the values for the customString field currently?
If you push headers through REST API using the PUT method, it overwrites each record entirely meaning that any field not included will be reset. I think that behavior may be affecting you if you are importing the customString fields separately.

To avoid the PUT method resetting fields coming from different imports, you could use a combination of POST (creates new records only) + PATCH (partially updates existing records only).

Side note: Mark it seems you may have 2 accounts:
image

11

I think this might be a similar issue we are having as well. We have started updating well headers through the rest API and it appears that if we update custom columns manually through the front end or load in data to a custom column using a spreadsheet the custom column gets cleared out after a rest API update even if we aren’t mapped to that particular custom header column. Is it not possible to not have custom columns cleared out when header data is updated using the rest API?

12

Yes, it’s possible, see my previous comment above.

If you push headers through REST API using the PUT method, it overwrites each record entirely meaning that any field not included will be reset. I think that behavior may be affecting you if you are importing the customString fields separately.

To avoid the PUT method resetting fields coming from different imports, you could use a combination of POST (creates new records only) + PATCH (partially updates existing records only).

Regards

1 Like