Forecast

the forecast table stores internal/customer forecasts for a well, which can be compared against prodx's pi based forecasts in the application's variance reports customer forecasts are not versioned in prodx — at any point in time there is one customer forecast per well the unique constraint on forecast entries is uwi + date replacing a forecast if a new version of a forecast uses the same dates as the old one, just push it — the upsert overwrites the existing records if the dates differ , delete the well's old forecast first otherwise the new points insert alongside the old ones and the well ends up with a mix of both forecasts variable data type unit of measure is nullable? default value description uwi string no unique well identifier must match the uwi of a record in the well docid\ p xhbe4jqkjqemay7aol5 table date datetime offset no forecast date datetime offset (with timezone) in iso 8601 format example 2022 09 27t16 28 37 +0000 oilrate double stb/d no forecasted oil rate gasrate double mscf/d no forecasted gas rate waterrate double stb/d no forecasted water rate data integrity checks condition response uwi is null or empty record rejected uwi does not exist in the well table record rejected any non nullable field is null record rejected common error messages api scenario error response add / upsert forecast unknown uwi uwi xxx does not exist fetch / delete forecast unknown uwi uwi xxx does not exist