Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

EnterpriseCrmEventbusProtoField

import type { EnterpriseCrmEventbusProtoField } from "https://googleapis.deno.dev/v1/integrations:v1.ts";

Information about the value and type of the field.

interface EnterpriseCrmEventbusProtoField {
cardinality?: "UNSPECIFIED" | "OPTIONAL";
fieldType?:
| "DATA_TYPE_UNSPECIFIED"
| "STRING_VALUE"
| "INT_VALUE"
| "DOUBLE_VALUE"
| "BOOLEAN_VALUE"
| "PROTO_VALUE"
| "SERIALIZED_OBJECT_VALUE"
| "STRING_ARRAY"
| "INT_ARRAY"
| "DOUBLE_ARRAY"
| "PROTO_ARRAY"
| "PROTO_ENUM"
| "BOOLEAN_ARRAY"
| "PROTO_ENUM_ARRAY"
| "BYTES"
| "BYTES_ARRAY"
| "NON_SERIALIZABLE_OBJECT"
| "JSON_VALUE";
protoDefPath?: string;
referenceKey?: string;
}

§Properties

§
cardinality?: "UNSPECIFIED" | "OPTIONAL"
[src]

By default, if the cardinality is unspecified the field is considered required while mapping.

§

This holds the default values for the fields. This value is supplied by user so may or may not contain PII or SPII data.

§
fieldType?: "DATA_TYPE_UNSPECIFIED" | "STRING_VALUE" | "INT_VALUE" | "DOUBLE_VALUE" | "BOOLEAN_VALUE" | "PROTO_VALUE" | "SERIALIZED_OBJECT_VALUE" | "STRING_ARRAY" | "INT_ARRAY" | "DOUBLE_ARRAY" | "PROTO_ARRAY" | "PROTO_ENUM" | "BOOLEAN_ARRAY" | "PROTO_ENUM_ARRAY" | "BYTES" | "BYTES_ARRAY" | "NON_SERIALIZABLE_OBJECT" | "JSON_VALUE"
[src]

Specifies the data type of the field.

§
protoDefPath?: string
[src]

Optional. The fully qualified proto name (e.g. enterprise.crm.storage.Account). Required for output field of type PROTO_VALUE or PROTO_ARRAY. For e.g., if input field_type is BYTES and output field_type is PROTO_VALUE, then fully qualified proto type url should be provided to parse the input bytes. If field_type is *_ARRAY, then all the converted protos are of the same type.

§
referenceKey?: string
[src]

This holds the reference key of the workflow or task parameter. 1. Any workflow parameter, for e.g. $workflowParam1$. 2. Any task input or output parameter, for e.g. $task1_param1$. 3. Any workflow or task parameters with subfield references, for e.g., $task1_param1.employee.id$

§

This is the transform expression to fetch the input field value. for e.g. $param1$.CONCAT('test'). Keep points - 1. Only input field can have a transform expression. 2. If a transform expression is provided, reference_key will be ignored. 3. If no value is returned after evaluation of transform expression, default_value can be mapped if provided. 4. The field_type should be the type of the final object returned after the transform expression is evaluated. Scrubs the transform expression before logging as value provided by user so may or may not contain PII or SPII data.