Wellbore Microstring

microstrings are smaller strings run inside the tubing, used for chemical or foam injection the unique constraint on microstring entries is sourcewellboreid + sourceid variable data type unit of measure is nullable? default value description sourceid string no unique identifier of the microstring, to enable upserts sourcewellid string no source id for the well must match the sourceid of a record in the well docid\ p xhbe4jqkjqemay7aol5 table sourcewellboreid string no source id for the wellbore must match the sourceid of a record in the wellbore docid\ xpqwcas8awdawyssmvjy6 table topmd double ft yes 0 0 top measured depth of the microstring bottommd double ft no bottom measured depth of the microstring id double in no inner diameter of the microstring od double in no outer diameter of the microstring roughness double in yes 0 0006 absolute roughness coefficient of the microstring material rundate datetime offset yes date the microstring was run datetime offset (with timezone) in iso 8601 format example 2022 09 27t16 28 37 +0000 pulldate datetime offset yes date the microstring was pulled datetime offset (with timezone) in iso 8601 format wellbore microstring notes microstring data is optional currently it is used for effective diameter in tubing pressure traverses top measured depth notes if topmd is null, the system assumes 0 ft roughness notes if roughness is null, the compute engine applies 0 0006 in its place data integrity checks condition response any non nullable field is null or empty record rejected (sourcewellid, sourcewellboreid) does not match an existing wellbore row skipped partial success on bulk ingest rows referencing an unknown wellbore are skipped while the remaining rows are written the error response names each skipped row an error response therefore does not mean nothing was written common error messages api scenario error response add / upsert microstring unknown wellbore microstring with sourceid 'xxx' was skipped wellbore with sourcewellid 'xxx' and sourcewellboreid 'xxx' was not found