Please enable JavaScript to view this site.

Made in EU
Roller Forums

Roller API Data Model

Navigation: Schema: Data > Tables

TicketsByDate: Roller Tickets by Date

Catalog: Roller

Schema: Data

Primary Keys: TicketId

Label: Tickets by Date

Documentation:

The timespan covered by the start and end date can not exceed 7 days.

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: data/tickets

Insert Roller API URL: data/tickets

Update Roller API URL: data/tickets

Delete Roller API URL: data/tickets

Field Selection Method: NotRequired

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function TicketsByDate. 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

endDate

datetime

☑

 

Search end date, based on record modified date.

startDate

datetime

☑

 

Search start date, based on record modified date.

 

Columns of Table Function

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

Name

Data Type

Label

Required

Documentation

bookingDate

datetime

Booking Date

☐

Booking date of the ticket - when the ticket is valid for/from.

createdDate

datetime

Created

☑

Date the ticket was created.

customerId

string

Customer ID

☐

Unique identifier of the customer linked to the ticket.

customTicketId

string

 

☐

Ticket identifier specified manually by the user e.g. the code from a pre-printed membership card.

expiryDate

datetime

Expires

☑

Date the ticket is no longer valid.

name

string

Name

☐

Ticket holder name.

numberOfRecurringPayments

int32

Number of Recurring Payments

☐

Number of recurring payments.

productId

string

Product ID

☐

Unique identifier of the product the ticket is for.

productSubType

string

Product Sub-type

☐

The sub type/variation of the product.

productType

string

Product Type

☑

The type/variation of the product.

recurringPaymentFrequency

string

Recurring Payment Frequency

☐

Recurring payment frequency.

ticketId

string

Ticket ID

☑

Unique identifier of the ticket.

 

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