# Create or Update Batch DayInterval Create or Update multiple DayInterval at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /day-intervals-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Request fields (application/json): - `interval_Year` (integer, required) Year of the date or interval used in internal date calculations - `interval_Month` (integer, required) Month of the date or interval used in internal date calculations - `interval_Day` (integer, required) Day of the date or interval used in internal date calculations - `day_From_Date` (string,null) Date and time stamp of the beginning of the specified day - `day_Name` (string,null) Full name of the day of the week - `day_Short_Name` (string,null) Abbreviated name of the day of the week - `day_Thru_Date` (string,null) Date and time stamp of the end of the specified day - `entry_Date` (string) Date record was first added to the system - `entry_User` (string,null) User that first added the record to the system - `holiday` (boolean, required) Bit indicating if the specified day falls on recognized holiday - `month_From_Date` (string,null) First day of the month containing the date specified - `month_Thru_Date` (string,null) Last day of the month containing the date specified - `quarter` (integer,null) Number indicating the quarter containing the date specified - `quarter_From_Date` (string,null) First day of the quarter containing the date specified - `quarter_Thru_Date` (string,null) Last day of the quarter containing the date specified - `update_Date` (string) Date the record was last updated in the system - `update_User` (string,null) User that last updated the record in the system - `week_Day` (integer,null) Number of the day of the week where Sunday is 1 - `weekend` (boolean,null) Bit indicating if the specified day falls on the weekend - `yearMonthDay_Seq` (integer,null) Sequence number used for simple date comparisons ## Response 207 fields (text/plain): - `data` (array,null) - `data.id` (array, required) List of key/value pairs that represent the unique id for the entity operation. - `data.id.key` (string,null) - `data.id.value` (any,null) - `data.status` (integer, required) http status of the operation (eg, 200, 201, 500) - `data.body` (string, required) operation message (eg, Updated, Created, Error message) - `error` (object) - `error.detail` (string,null) A human-readable explanation specific to this occurrence of the problem. - `error.instance` (string,null) A URI reference that identifies the specific occurrence of the problem.It may or may not yield further information if dereferenced. - `error.status` (integer) The HTTP status code([RFC7231], Section 6) generated by the origin server for this occurrence of the problem. - `error.title` (string,null) A short, human-readable summary of the problem type.It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization(e.g., using proactive content negotiation; see[RFC7231], Section 3.4). - `error.type` (string,null) A URI reference [RFC3986] that identifies the problem type. This specification encourages that, when dereferenced, it provide human-readable documentation for the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member is not present, its value is assumed to be "about:blank". - `debug` (object) - `debug.activityID` (string, required) ## Response 401 fields