# Create or Update Batch NoteReference Create or Update multiple NoteReference at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /note-references-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Request fields (application/json): - `reference_Key` (integer, required) ID of the note reference. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `column_Name1` (string, required) Defines the subject of 'Key_Value1'. - `column_Name2` (string,null) Defines the subject of 'Key_Value2'. - `column_Name3` (string,null) Defines the subject of 'Key_Value3'. - `column_Name4` (string,null) Defines the subject of 'Key_Value4'. - `column_Name5` (string,null) Defines the subject of 'Key_Value5'. - `column_Type1` (string,null) Identifies the type of data of the value specified by 'Key_Value1'. - `column_Type2` (string,null) Identifies the type of data of the value specified by 'Key_Value2'. - `column_Type3` (string,null) Identifies the type of data of the value specified by 'Key_Value3'. - `column_Type4` (string,null) Identifies the type of data of the value specified by 'Key_Value4'. - `column_Type5` (string,null) Identifies the type of data of the value specified by 'Key_Value5'. - `entry_Date` (string) Date record was first added to the system - `entry_User` (string,null) User that first added the record to the system - `key_Value1` (string, required) Value of the subject specified by 'Column_Name1'. - `key_Value2` (string,null) Value of the subject specified by 'Column_Name2'. - `key_Value3` (string,null) Value of the subject specified by 'Column_Name3'. - `key_Value4` (string,null) Value of the subject specified by 'Column_Name4'. - `key_Value5` (string,null) Value of the subject specified by 'Column_Name5'. - `navigate_Object` (string,null) PowerBuilder object connected to the note that is used for navigation - `note_Key` (integer, required) ID of the associated note. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `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 ## 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