In this administrative section, the entire sales department of Business Central is joined with the Entertainment part, i.e. this is where the ticket admission schedule lines are connected to the Item entities (by joining the Item No. with the created Admission Code). All individual tickets stored in the database are listed here, and it’s possible to configure them by adding more details or attaching specific behaviors to them.
|Specifies the identification number of an item created in the ERP system that is used in the POS for selling a specific ticket.
|Specifies the code that is added to the value in the Item No. column to create a family of tickets (e.g. according to the attendees age). This is usually used when setting a web ticket. Only one dimension of variants is supported by Microsoft.
|Specifies the code of the admission the ticket can be used for. Tickets offer different levels of clearance, and they may allow access to multiple venues.
|When there are multiple admissions associated with one ticket, and, for example, the POS is set up to create an admission on sale, the POS will select the default admission code specified here. This feature is used throughout the solution, if no code is specified, while there are multiple codes to choose from. An error will occur if the default admission isn’t defined, and multiple options to choose from are present.
|The ticket quantity is multiplied by this number to calculate the capacity cost. For normal use, the quantity should be set to 1; for group tickets, it can be the same as the number of group participants; for a person with disabilities who needs a companion, the quantity can be set to 2.
|Ticket Schedule Selection
|Specifies the default POS schedule selection behavior, intended to provide a smart-assist for the walk-up ticket process. The following options are available: Same As Admission, Today, Next Available, Schedule Entry Required, None.
|Sales From Date/Sales Until Date
|Specifies the date from which the ticket can be purchased and the date until which the ticket can be purchased respectively.
|Enforce Schedule Sales Limits
|Specify whether the dates specified in Sales From Date and Sales Until Date fields are enforced.
|Admission Entry Validation
|When the Ticket Configuration Source field on the Ticket Type specifies the option TICKET_BOM, this field’s value is used instead of the corresponding field in Ticket Type. It specifies how many times the ticket can be validated when admitting the entry.
|Determines which event needs to precede the ticket being recorded as admitted. The available options are On Scan, On Sale, Always, and Per Unit.
|Percentage of Adm. Capacity
|Specifies the percentage of maximum admission capacity for the provided item.
|POS Sale May Exceed Capacity
|If ticket, the maximum capacity can be exceeded when the ticket is sold in the POS.
|Max No. of Entries
|When the Ticket Configuration Source field on the Ticket Type specifies the option TICKET_BOM, this field’s value is used instead of the corresponding field in Ticket Type. Determines the maximum number of entries to the admission that can be made before the ticket becomes invalid.
|Admission Dependency Code
|Specifies if some events/locations are mutually exclusive, or if there are locations/events managed by the ticket that need to be visited in a specific order.
|Revisit Condition (Statistics)
|Specifies how to determine a unique visitor when a ticket is used more than once.
|When the Ticket Configuration Source field on the Ticket Type specifies the option TICKET_BOM, this field’s value is used instead of the corresponding field in Ticket Type. The formula provided here determines the period during which the ticket is valid.
|Allow Rescan Within (Sec.)
|Specifies the number of seconds after the scan during which the ticket can be rescanned, even though the ticket only allows a single admission. If no value is stated, the ticket can’t be scanned (assuming a single entry is allowed).
|The information you provide in this field will be included in the printed ticket as additional information.
|Specifies useful information about the admission that can be included on a printed card.
|If set to Cut-Off, you can specify how much in advance before the event starts will it be possible to reschedule.
|Reschedule Cut-Off (Hours)
|Specifies after how many hours it will be possible to reschedule if the Cut-Off (Hours) is selected in the Reschedule Policy column.
|Specifies whether it’s possible to receive a refund for a ticket.
|Notification Profile Code
|Specifies which events will trigger notifications to be sent to the ticket-holder. This option is useful in the CRM context.
|Refund Price %
|Specifies the percentage of the ticket price that is refunded to customers (provided that refunds are performed).
|Preferred Sales Display Method
|Specifies what is the ticket scheduling going to be displayed like - as a calendar or a schedule.
|Ticket Base Calendar Code
|You can specify the days on which the venue will not be working, e.g. for a public holiday. The system takes note of this, and makes sure the tickets on those selected days are never created.
|Specifies variations to the base calendar, if any.
|Publish as eTicket
|Specifies that this ticket should be published using the Apple Wallet technology.
|eTicket Type Code
|Specifies the ticket design options used for displaying the ticket in the eWallet.
|Publish Ticket URL
|Specifies the URL to the server on which you can share the ticket with customers.
|When the Ticket Configuration Source field on the Ticket Type specifies the option TICKET_BOM, this field’s value is used instead of the corresponding field in Ticket Type.