Dataflow Property Element
Attributes
| Attribute | API Type | Default | Description |
|---|---|---|---|
| DataType | SsisDataflowPropertyDataType | Empty | This value specifies the type of the variable that should be assigned to the custom dataflow property. This is a required property |
| Name | String | Specifies the name of the object. This name can be used to reference this object from anywhere else in the program. This is a required property | |
| ContainsId | Boolean | False | Indicates whether this property contains a data linage column id. |
| Description | String | This value stores the description that is emitted in SSIS for the data flow property. | |
| IsArray | Boolean | False | This value specifies whether the dataflow property is an array of values. |
| LineageIdListSeparator | String | In the case of a list of lineage ids, this property specifies the string sequence that is used to separate items in the list. The same separator is used both for extracting column name lists and emitting the list of translated lineage ids. | |
| State | SsisComponentPropertyPersistState | Default | Specifies how the property is persisted in the package XML. |
| SupportsExpression | Boolean | False | This value specifies whether the custom dataflow property support the use of SQL Server Integration Services expressions in the value. |
| TranslateValueToLineageId | Boolean | False | Specifies whether the compiler should translate the property value or values into SSIS lineage ids during emission. This property is used in combination with the LineageIdListSeparator property, if a list of lineage ids is expected. |
| TypeConverter | String | This value specifies the name of the type converter to use. | |
| UITypeEditor | String | This value specifies the name of the user interface type editor that should be used for this custom dataflow property. |
Collection Children
| Child | API Type | Description |
|---|---|---|
| <Annotations> <Annotation /> </Annotations> | AstAnnotationNode | This is a collection of annotation items that can be used to specify documentation, tags, or other information. Annotations are particularly useful for storing information about nodes that can be used by BimlScript code. |