# Update NoteData Updates a specific NoteData. Endpoint: PUT /note-data/{noteKey} Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Path parameters: - `noteKey` (integer, required) Note Key ## Request fields (application/json): - `note_Key` (integer, required) Key value used to identify a specific note - `effective_Date` (string,null) Date the information in the note goes into effect - `entry_Date` (string) Date record was first added to the system - `entry_User` (string,null) User that first added the record to the system - `note_Alert` (boolean, required) Flag identifying if there is an alert associated with the note - `note_Alert_End` (string,null) Date the alert associated with a note terminates - `note_Category` (string,null) Identifies the 'Category' of note. Note 'Category' are configured within 'Note Configuration'. - `note_Data` (string,null) Text data of the note. - `note_Priority` (string,null) Identifies the 'Priority' of note. Note 'Priority' are configured within 'Note Configuration'. - `note_Subject` (string,null) Description of the note's subject. - `note_Type` (string,null) Identifies the 'Type' of note. Note 'Types' are configured within 'Note Configuration'. - `term_Date` (string,null) Date the information in the note terminates - `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 200 fields (text/plain): - `data` (object) - `data.note_Key` (integer, required) Key value used to identify a specific note - `data.effective_Date` (string,null) Date the information in the note goes into effect - `data.entry_Date` (string) Date record was first added to the system - `data.entry_User` (string,null) User that first added the record to the system - `data.note_Alert` (boolean, required) Flag identifying if there is an alert associated with the note - `data.note_Alert_End` (string,null) Date the alert associated with a note terminates - `data.note_Category` (string,null) Identifies the 'Category' of note. Note 'Category' are configured within 'Note Configuration'. - `data.note_Data` (string,null) Text data of the note. - `data.note_Priority` (string,null) Identifies the 'Priority' of note. Note 'Priority' are configured within 'Note Configuration'. - `data.note_Subject` (string,null) Description of the note's subject. - `data.note_Type` (string,null) Identifies the 'Type' of note. Note 'Types' are configured within 'Note Configuration'. - `data.term_Date` (string,null) Date the information in the note terminates - `data.update_Date` (string) Date the record was last updated in the system - `data.update_User` (string,null) User that last updated the record in the system - `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