# FutureEventAllocations: Tixly Future Event Allocations
Fetches only those events you have access to that have a start date in the future. You are able to filter these by Edited dates.
## Documentation
Fetches only those events you have access to that have a start date in the future. You are able to filter these by Edited dates.
- Catalog: `Tixly`
- Schema: `Event`
- Label: Future Event Allocations
This is a read-only table function. The Tixly API may not support changing the data or the Invantive UniversalSQL driver for Tixly does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Tixly API.
## Parameters of Table Function
The following parameters can be used to control the behaviour of the table function `FutureEventAllocations`. 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 |
|---|:---:|:---:|:---:|---|
| `EditedFrom` | `` | ☐ | | Get events edited after this date |
| `EditedTo` | `` | ☐ | | Get events edited before this date |
## Columns of Table Function
The columns of the table function `FutureEventAllocations` are shown below. Each column has an SQL data type.
| Name | Data Type | Label | Required | Documentation |
|---|:---:|---|:---:|---|
| `Abbreviation` | `varchar2` | Abbreviation | ☐ | The abbreviation of the allocation type on the event |
| `AccountNumber` | `varchar2` | | ☐ | |
| `AdminName` | `varchar2` | | ☐ | |
| `Allocated` | `int32` | Allocated | ☐ | |
| `AllocationTypeId` | `int32` | | ☐ | The unique id of the allocation type |
| `AvailableOnline` | `char` | Available Online | ☐ | |
| `Block` | `char` | Block | ☐ | Is the allocation type blocked, meaning that they are excluded from the capacity of the event |
| `BlockedAllocated` | `int32` | Blocked Allocated | ☐ | |
| `Capacity` | `int32` | Capacity | ☐ | |
| `CreatedUTCUnix_2` | `int64` | | ☐ | |
| `CreatedUTCUnix` | `int64` | | ☐ | |
| `Created_2` | `datetime` | | ☐ | |
| `Created` | `datetime` | Created | ☐ | |
| `DateConfirmed` | `char` | Date Confirmed | ☐ | |
| `DepartmentNumber` | `varchar2` | | ☐ | |
| `Dimension1` | `varchar2` | | ☐ | |
| `Dimension2` | `varchar2` | | ☐ | |
| `Dimension3` | `varchar2` | | ☐ | |
| `Dimension4` | `varchar2` | | ☐ | |
| `Dimension5` | `varchar2` | | ☐ | |
| `Dimension6` | `varchar2` | | ☐ | |
| `Dimension7` | `varchar2` | | ☐ | |
| `Dimension8` | `varchar2` | | ☐ | |
| `EditedUTCUnix` | `int64` | | ☐ | |
| `Edited` | `datetime` | Edited | ☐ | |
| `EndDateUTCUnix` | `int64` | | ☐ | |
| `EndDate` | `datetime` | End Date | ☐ | |
| `EventAllocationId` | `int32` | | ☐ | The unique id of the allocation type on the specific event |
| `EventGroupId` | `int32` | Event Group ID | ☐ | |
| `EventGroup` | `varchar2` | Event Group | ☐ | |
| `ExpiresHoursBefore` | `int32` | Expires Hours Before | ☐ | How many hours before the event does the allocation type expire |
| `ExternalReferenceNumber` | `varchar2` | | ☐ | |
| `HallConfigurationId` | `int32` | | ☐ | |
| `HallId` | `int32` | Hall ID | ☐ | |
| `Hall` | `varchar2` | Hall | ☐ | |
| `Id_2` | `int32` | | ☐ | |
| `Id` | `int32` | ID | ☐ | The Id is the same as AllocationTypeId and is the unique id of the allocation type
that was used, the name and expirations can be changed per event and therefore to
be able to map the specific allocations to seats then use the EventAllocationId as
that's unique per allocation and the event where it's used. |
| `IsFreeEvent` | `char` | Is Free Event | ☐ | |
| `IsNumbered` | `char` | Is Numbered | ☐ | |
| `Name_2` | `varchar2` | | ☐ | |
| `Name` | `varchar2` | Name | ☐ | The name of the allocation type on the event |
| `OnlineReservationAllowed` | `char` | Online Reservation Allowed | ☐ | |
| `OrganisationId` | `int32` | Organisation ID | ☐ | |
| `PromoterId` | `int32` | Promoter ID | ☐ | |
| `Promoter` | `varchar2` | Promoter | ☐ | |
| `ReservedTickets` | `int32` | Reserved Tickets | ☐ | Total number of seats reserved in the allocation |
| `Reserved` | `int32` | Reserved | ☐ | |
| `SaleStatusId` | `int32` | Sale Status ID | ☐ | |
| `SeasonId` | `int32` | Season ID | ☐ | |
| `Season` | `varchar2` | Season | ☐ | |
| `Seats` | `int32` | Seats | ☐ | Total number of seats that have the allocation |
| `SoldTickets` | `int32` | Sold Tickets | ☐ | Total number of seats sold in the allocation |
| `Sold` | `int32` | Sold | ☐ | |
| `StartDateUTCUnix` | `int64` | | ☐ | |
| `StartDate` | `datetime` | Start Date | ☐ | |
| `SubTitle` | `varchar2` | Subtitle | ☐ | |
| `Vat` | `double` | VAT | ☐ | |
| `VenueId` | `int32` | Venue ID | ☐ | |
| `Venue` | `varchar2` | Venue | ☐ | |