> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/siriusware/flaik-siriusware-integration-standards/siriusware-1.md).

# Siriusware Guest Preferences Mapping (User-Defined Fields)

## Introduction

To ensure that guest data flows seamlessly from the Siriusware system to the flaik database, it is essential to map the user-defined fields correctly. This section outlines the steps and considerations for configuring and mapping these fields.

### Standard Mappings

Below are the standard mappings required to send guest data from Siriusware to flaik. Non-standard and custom requirements may incur additional implementation fees.

#### Siriusware Table/View Name

The guest info table/view name in Siriusware will vary depending on the version of Sirusware you are using.

<table><thead><tr><th width="321">Version</th><th width="350">Table/View Name</th></tr></thead><tbody><tr><td>Siriusware v4 (Not encrypted)</td><td>guests</td></tr><tr><td>Siriusware v4 (Encrypted)</td><td>SiriusV_DecryptedGuests</td></tr><tr><td>Siriusware v5</td><td>SiriusV_DecryptedGuests</td></tr></tbody></table>

#### Standard flaik Guest Profile fields

These are the standard guest information mappings used by flaik.

<table><thead><tr><th width="157">flaik Field</th><th width="143">V4</th><th width="146">V4 (encrypt)</th><th width="148">V5 (encrypt)</th></tr></thead><tbody><tr><td>UniquePersonId</td><td>guest_no</td><td>guest_no</td><td>guest_no</td></tr><tr><td>FirstName</td><td>first_name</td><td>first_name</td><td>FirstName</td></tr><tr><td>LastName</td><td>last_name</td><td>last_name</td><td>LastName</td></tr><tr><td>Email</td><td>e_mail</td><td>e_mail</td><td>EMail</td></tr><tr><td>GenderCode</td><td>gender</td><td>gender</td><td>Gender</td></tr><tr><td>PersonDOB</td><td>birth_date</td><td>Birth_Date</td><td>BirthDate</td></tr></tbody></table>

#### Optional/Mapped fields

The following list of user-defined fields can be mapped to different fields in flaik as needed.

| text\_1   |
| --------- |
| text\_2   |
| text\_3   |
| text\_4   |
| text\_5   |
| text\_6   |
| text\_7   |
| text\_8   |
| ltext\_1  |
| ltext\_2  |
| ltext\_3  |
| ltext\_4  |
| ltext\_5  |
| number\_1 |
| number\_2 |
| number\_3 |
| number\_4 |
| number\_5 |
| memo\_1   |
| memo\_2   |
| memo\_3   |
| memo\_4   |
| notes     |

Any of the user-defined fields above can be mapped to any of the fields in flaik outlined below:

| Date of Birth                                                         |
| --------------------------------------------------------------------- |
| Email                                                                 |
| Contact Number                                                        |
| Gender                                                                |
| Medication                                                            |
| Food Allergy                                                          |
| Drug Allergy                                                          |
| Special Condition                                                     |
| Ability Level Ski                                                     |
| Ability Level Snowboard                                               |
| Ability Level Nordic                                                  |
| Ability Level Telemark                                                |
| Ability Level Adaptive Ski                                            |
| Ability Level Adaptive Snowboard                                      |
| Generic Discipline                                                    |
| Generic Ability Level                                                 |
| Guest Note (Sale note if the guest is associated to a private lesson) |
| Primary Emergency contact name                                        |
| Primary Emergency contact phone                                       |
| Alternative Emergency contact name                                    |
| Alternative Emergency contact phone                                   |

By following these mapping guidelines, resorts can ensure that all guest data is accurately transferred from Siriusware to flaik, facilitating better guest management and service delivery.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/siriusware/flaik-siriusware-integration-standards/siriusware-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.