--- alias: user-guide-automation-task-opcua-addcustomdatatypes tags: - automation tasks description: "This documentation details adding custom data types to an OPCUA Server task" --- # Add Custom Data Types ![Screenshot showing a dialog box for adding custom data types.](images/customdatatypes-lg.svg) This task allows adding custom data types to an OPCUA Server (connect-iot instance) ![Screenshot showing a dialog box for adding custom data types.](./images/add_custom_data_types_parameters.png) !!! warning This task is currently deprecated and will be removed in future versions. ## Inputs | Name | Data Type | Values | Description | |-----------------|-----------|--------|-----------------------------------------| | customDataTypes | `any` | | Supply the dataTypes to create by input | | Activate | `any` | Yes | Activates the task | ## Outputs | Name | Data Type | Values | Description | |---------|-----------|--------|-------------------------------------------------| | rawData | `any` | | The created DataTypes | | Success | `Boolean` | | Result of the method execution | | Error | `Error` | | Used to report an error in the method execution | ## Settings On the *General Tab*, you have the usual settings: ![Screenshot showing a settings page with options for custom data types.](./images/add_custom_data_types_settings.png) On the *Custom Data Types* Tab, you have entries for each of the result parameters of the command: ![Screenshot showing the "Add Custom Data Types" settings page.](./images/add_custom_data_types_settings_datatypes.png) ## Behavior The task should be activated before connecting to the driver (onInitialize -> activate task -> connect). Custom DataType names don't need to end with `DataType` because this suffix will be automatically appended to each name. DataTypes can be inserted using settings or by input. Input value overrides settings values. ## Remarks None.