# Create or Update Batch ReportDefinition

Create or Update multiple ReportDefinition at once.  If the entity exists, it will be updated.  If the entity does not exist, it will be created.

Endpoint: PUT /report-definitions-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

  - `vbasoftware-database` (string, required)
    Target database

## Request fields (application/json):

  - `reportDefinition_Key` (integer, required)
    ID of the report definition. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `bR_Report_ID` (string,null)
    Contains the GUID for the corresponding Advanced Reporting ID in Bold Reports.

  - `combine_Navigation` (boolean, required)
    This will combine the results of a criteria window with multiple criteria. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `criteria_Object` (string,null)
    The PowerBuilder object used to enter criteria.

  - `custom_Report` (string,null)
    Identifies a custom report to be used.

  - `entry_Date` (string)
    Date record was first added to the system

  - `entry_User` (string,null)
    User that first added the record to the system

  - `exclude_Adjustment_Category` (boolean, required)
    Flag indicating if the adjustment category should be excluded from the report Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `exclude_Other_Category` (boolean, required)
    Flag indicating if the other category should be excluded from the report Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `exclude_Total_Category` (boolean, required)
    Flag indicating if the total category should be excluded from the report Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `group_Categories_Only` (boolean, required)
    Limits the report to only showing Rate Categories defined at the Group, not all Rate Categories on the Invoice. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `help_File` (string,null)
    Help file associated with the report object

  - `help_Topic_ID` (integer,null)
    Topic ID within the help file associated with the report object

  - `invoice_Category_Column_Count` (integer,null)
    Identifies how many category columns are used within the report.

  - `navigation_Report` (boolean, required)
    Indicates that the report has navigation. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `report_Category` (string,null)
    Identifies which category the report belongs to.

  - `report_Description` (string, required)
    Full description of the report.

  - `report_Detail_Object` (string,null)
    Specifies a secondary report that may be used in conjunction with the main report

  - `report_Example` (string,null)
    Utilize the file explorer to choose an example of the chosen report.

  - `report_ID` (string, required)
    ID of the report being defined.

  - `report_Library` (string,null)
    Identifies which report library the User wishes to choose from.

  - `report_Name` (string, required)
    Name of the report.

  - `report_Object` (string,null)
    Indicates which report will be used with the automation step.

  - `schedule_Report` (boolean, required)
    Indicates that the report may be used with scheduling functionality. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `series_Report` (boolean, required)
    Indicates that the report may be added to a report series. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `trackable_Report` (boolean, required)
    Indicates that tracking functionality will be used for the report. 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

  - `vbA_Canned_Report` (boolean)

## 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