| Table of Contents |
|---|
| minLevel | 1 |
|---|
| maxLevel | 2 |
|---|
| outline | false |
|---|
| style | none |
|---|
| type | flat |
|---|
| printable | true |
|---|
|
...
This operation returns all the values of a historical lookup row into a JSON field upon successful key correlation.
| Info |
|---|
Existing lookups required To perform these operations, it is necessary to have existing lookups ready for use (visit this article to get help uploading lookups and this article to get help creating query lookups). |
How does it work in the search window?
...
Argument | Description | Data type |
|---|
Lookup name mandatory | Choose the lookup you want to use to enrich your table. | string |
Key mandatory | Choose the table field you want to use to find matches with the lookup key field. | same as lookup key field |
Time | Choose the table timestamp you want to use to correlate with the lookup timestamp. It identifies the row with the highest latest timestamp in the lookup that is before the timestamp in your table. | timestamp | | Info |
|---|
Existing lookups required
To perform these operations, it is necessary to have existing lookups ready for use (visit this article to get help uploading lookups and this article to get help creating query lookups). |
Once you specify the adequate arguments and click the Create field button, the new field is added to your table.
...
select hlurjson("Lookup_name", Key_field, Timestamp_field) as new_field
| Info |
|---|
Existing lookups required
To perform these operations, it is necessary to have existing lookups ready for use (visit this article to get help uploading lookups and this article to get help creating query lookups). |
|---|
Syntax considerations - → This must be the name of lookup that contains the data you want to use to enrich your data. The name of an inexistent lookup will return an error when running the query.
- → This must be the table field that will be used to correlate find matches with the lookup key. The name can be different than the lookup key field as long as the data type coincide and the values it contains are potential matches (username-user). The absence of matches will return null and a different data type will return an error when running the query .
| Status |
|---|
| colour | Green |
|---|
| title | timestamp_field |
|---|
|
→ This must be the table timestamp that will be used to correlate with the lookup timestamp. A data type other than timestamp will return an error when running the query.
|
...
