Table of Contents | ||||
---|---|---|---|---|
|
...
Input | This Snap has at least two document input views. |
---|---|
Output | This Snap has exactly one document output view. |
Error | This Snap has at most one document error view. |
Troubleshooting
None.
Limitations and Known Issues
...
Label | Required. The name for the Snap. You can modify this to be specific, especially if you have more than one of the same Snap in your pipeline. | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Policy | Specify the base and reference datasets and fields. | |||||||||||
Base view | The input view to which the base dataset is connected. Default value: input0 (name of the input view) | |||||||||||
Base path | The field in the base dataset that is to be used as the base field. This has to be the common identifier for joining with the reference dataset(s). Example: $customer_id Default value: [None] | |||||||||||
Ref view | View where the reference dataset is the input. Default value: input0 (name of the input view) | |||||||||||
Ref path | The field in the reference dataset that is to be used. This field must have the same values as in the base field. Example: $customer_id Default value: [None] | |||||||||||
| TBA once this field's functionality is finalized.
|
|
Examples
Getting Customer Insights Based on Transaction Data
...