# Container Output: Several Data Type unsupported

**URL:** <https://forum.knime.com/t/container-output-several-data-type-unsupported/74851>\
**Category:** Feedback & Ideas\
**Tags:** bug\
**Created:** [October 30, 2023, 11:57am UTC](https://forum.knime.com/t/container-output-several-data-type-unsupported/74851 "2023-10-30T11:57:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [October 30, 2023, 11:57am UTC](https://forum.knime.com/t/container-output-several-data-type-unsupported/74851/1 "2023-10-30T11:57:30Z")

</div>

Hi,

I happen to encounter an issue when calling a remote workflow where the Container Output is not supporting unknown data types. Since it is sometimes not possible to guarantee data type consistency and the Container Output not really processing but merely passing data through, why not enabling it to be more generous about unknown data types?

```auto
ERROR Container Output (Table) 6:1050 Execute failed: The column type: "?" is not supported
ERROR Call Workflow (Table Based) 3:1323 Execute failed: Failure, workflow was not executed, current state is IDLE.
Container Output (Table) 6:1050: Execute failed: The column type: "?" is not supported

```

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/2/f/2fc17fa956ae937891fd9912c53e1ccae935df42.jpeg)

UPDATE: It seems the data type “set” and who knows what else, is not supported either. This is … unsettling.

`ERROR Call Workflow (Table Based) 3:1323 Execute failed: Unsupported data type: "Set"`

Best  
Mike

---

<div class="post-metadata">

**Author:** ![AlexanderFillbrunn](https://forum-cdn.knime.com/user_avatar/forum.knime.com/alexanderfillbrunn/32/357_2.png) [@AlexanderFillbrunn](https://forum.knime.com/u/AlexanderFillbrunn)\
**Post date:** [October 30, 2023, 1:18pm UTC](https://forum.knime.com/t/container-output-several-data-type-unsupported/74851/2 "2023-10-30T13:18:12Z")

</div>

Hi Mike,  
For full data type and port support, I recommend [Workflow Services](https://docs.knime.com/2021-12/analytics_platform_workflow_invocation_guide/index.html#workflow-services-intro). The container output node produces JSON and not all data types can be converted to that (I agree though, that for a set type it could be possible).  
Kind regards,  
Alexander

---

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [October 30, 2023, 2:39pm UTC](https://forum.knime.com/t/container-output-several-data-type-unsupported/74851/3 "2023-10-30T14:39:47Z")

</div>

Hi @AlexanderFillbrunn,

I am using these already as it’s about the Container Output node:

> **[Container Output (Table)](https://hub.knime.com/knime/extensions/org.knime.features.json/latest/org.knime.json.node.container.output.table.ContainerTableOutputNodeFactory)**
>
> This node sends a table to an external caller (i.e. the Call Workflow (Table Based) node or an external REST client). A configured parameter makes the Containe…

Best  
Mike

---

<div class="post-metadata">

**Author:** ![AlexanderFillbrunn](https://forum-cdn.knime.com/user_avatar/forum.knime.com/alexanderfillbrunn/32/357_2.png) [@AlexanderFillbrunn](https://forum.knime.com/u/AlexanderFillbrunn)\
**Post date:** [October 30, 2023, 3:31pm UTC](https://forum.knime.com/t/container-output-several-data-type-unsupported/74851/4 "2023-10-30T15:31:19Z")

</div>

Hi Mike,  
For it to be a workflow service, you would need to use the [Workflow Service Input](https://kni.me/n/SjCp1LKYnOOV8KMB) and [Workflow Service Output](https://kni.me/n/9xSDVHDks-V8M3VU) nodes in connection with the [Call Workflow Service](https://kni.me/n/EkT0WUPnhzoKf3YG) node.  
Kind regards,  
Alexander

---

<div class="post-metadata">

**Author:** ![mwiegand](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mwiegand/32/66896_2.png) [@mwiegand](https://forum.knime.com/u/mwiegand)\
**Post date:** [October 30, 2023, 4:51pm UTC](https://forum.knime.com/t/container-output-several-data-type-unsupported/74851/5 "2023-10-30T16:51:57Z")

</div>

Hi @AlexanderFillbrunn,

maybe I am not quite getting the point you want to make but I am using the equivalent node Call Workflow (Table Based).

![image](https://forum-cdn.knime.com/uploads/default/original/3X/c/8/c8d5c120bf592041d50ffaf9a2630997b3ce82cd.png)

Best  
Mike

---

<div class="post-metadata">

**Author:** ![AlexanderFillbrunn](https://forum-cdn.knime.com/user_avatar/forum.knime.com/alexanderfillbrunn/32/357_2.png) [@AlexanderFillbrunn](https://forum.knime.com/u/AlexanderFillbrunn)\
**Post date:** [October 31, 2023, 8:31am UTC](https://forum.knime.com/t/container-output-several-data-type-unsupported/74851/6 "2023-10-31T08:31:25Z")

</div>

Hi Mike,  
The nodes are not equivalent. The Call Workflow (Table Based) in combination with the container in- and outputs uses JSON as transport protocol for your data, while the Workflow Service nodes use a proprietary binary format that can handle all KNIME types.  
Kind regards,  
Alexander