# PeopleEventsByWebsiteIdAndPeopleId: Crisp People Events ## Documentation Events stacked on a people profile, such as those registered with crp_people.add_people_event. - Catalog: `Crisp` - Schema: `Crisp` - Label: People Events This is a read-only table function. The Crisp API may not support changing the data or the Invantive UniversalSQL driver for Crisp does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Crisp API. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `PeopleEventsByWebsiteIdAndPeopleId`. 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 | |---|:---:|:---:|:---:|---| | `people_id` | `varchar2` | ☑ | | The people identifier, or the email address of the people profile. | | `people_id` | `varchar2` | ☑ | | The people identifier, or the email address of the people profile. | | `website_id` | `varchar2` | ☐ | | The website identifier. Defaults to the website ID of the connection when left out. | | `website_id` | `varchar2` | ☐ | | The website identifier. Defaults to the website ID of the connection when left out. | ## Columns of Table Function The columns of the table function `PeopleEventsByWebsiteIdAndPeopleId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `color` | `varchar2` | | ☐ | Colour of the event (if any); one of red, orange, yellow, green, blue, purple, pink, brown, grey and black. | | `color` | `varchar2` | | ☐ | Colour of the event (if any); one of red, orange, yellow, green, blue, purple, pink, brown, grey and black. | | `data` | `varchar2` | | ☐ | Data of the event as JSON (if any). | | `data` | `varchar2` | | ☐ | Data of the event as JSON (if any). | | `text` | `varchar2` | | ☑ | Text of the event. | | `text` | `varchar2` | | ☑ | Text of the event. | | `timestamp` | `datetime` | | ☑ | Timestamp at which the event was stacked. | | `timestamp` | `datetime` | | ☑ | Timestamp at which the event was stacked. |# PeopleEventsByWebsiteIdAndPeopleId: Crisp People Events ## Documentation Events stacked on a people profile, such as those registered with crp_people.add_people_event. - Catalog: `Crisp` - Schema: `Crisp` - Label: People Events This is a read-only table function. The Crisp API may not support changing the data or the Invantive UniversalSQL driver for Crisp does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Crisp API. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `PeopleEventsByWebsiteIdAndPeopleId`. 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 | |---|:---:|:---:|:---:|---| | `people_id` | `varchar2` | ☑ | | The people identifier, or the email address of the people profile. | | `people_id` | `varchar2` | ☑ | | The people identifier, or the email address of the people profile. | | `website_id` | `varchar2` | ☐ | | The website identifier. Defaults to the website ID of the connection when left out. | | `website_id` | `varchar2` | ☐ | | The website identifier. Defaults to the website ID of the connection when left out. | ## Columns of Table Function The columns of the table function `PeopleEventsByWebsiteIdAndPeopleId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `color` | `varchar2` | | ☐ | Colour of the event (if any); one of red, orange, yellow, green, blue, purple, pink, brown, grey and black. | | `color` | `varchar2` | | ☐ | Colour of the event (if any); one of red, orange, yellow, green, blue, purple, pink, brown, grey and black. | | `data` | `varchar2` | | ☐ | Data of the event as JSON (if any). | | `data` | `varchar2` | | ☐ | Data of the event as JSON (if any). | | `text` | `varchar2` | | ☑ | Text of the event. | | `text` | `varchar2` | | ☑ | Text of the event. | | `timestamp` | `datetime` | | ☑ | Timestamp at which the event was stacked. | | `timestamp` | `datetime` | | ☑ | Timestamp at which the event was stacked. |