Please enable JavaScript to view this site.

Roller Forums

Roller API Data Model

Navigation: Schema: Data > Tables

BookingItems: Roller Booking Items

Catalog: Roller

Schema: Data

Label: Booking Items

Documentation:

Search bookings by keywords, date and more. At least one search criteria is required. If there are more than 100 bookings only the latest 100 bookings are returned.

This is a read-only table function. The Roller API may not support changing the data or the Invantive SQL driver for Roller does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Roller API.

Select Roller API URL: bookings

Insert Roller API URL: bookings

Update Roller API URL: bookings

Delete Roller API URL: bookings

Field Selection Method: NotRequired

Base Path: bookings[*].item[*]

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function BookingItems. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.

Name

Data Type

Required

Default Value

Documentation

date

datetime

☐

 

Date of the bookings you are looking for.

keywords

string

☐

 

Keywords match against various properties of a booking including customer detail. Up to 10 bookings are returned. The newest bookings are returned when there are more than 10 matches found.

locationIds

string

☐

 

Comma separated capacity location IDs. Date is required.

productIds

string

☐

 

Comma separated product IDs. Date is required.

startTime

string

☐

 

Session start time (only applies to session products) e.g. 09:00 = 9am, 13:00 = 1pm. Date is required.

 

Columns of Table Function

The columns of the table function BookingItems are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

booking_bookingReference

string

 

☑

Unique identifier for a booking.

booking_createdDate

datetime

 

☑

Date the booking item was created.

booking_customerId

string

 

☐

Unique identifier of the customer linked to the booking.

booking_name

string

 

☐

Name of the booking can be different to the booking owner (defaults to the booking owner's name).

booking_status

string

 

☐

Booking status.

booking_total

decimal

 

☐

Total cost.

booking_uniqueID

guid

 

☐

Unique booking ID.

bookingDate

datetime

Booking Date

☐

The date this item was purchased or the date this item is valid for.

productId

int32

Product ID

☐

Unique identifier for a product.

quantity

int32

Quantity

☐

Number of items purchased - same as number of tickets except when GroupSize is greater than one.

startTime

string

 

☐

Session start time in 24hr format e.g. 11:30 = 11:30 AM.

 

22-09-2022 21:51 Version 22.0.355-PROD+3587

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer