# CatalystV2 field data array name causing issues

**URL:** https://discourse.paraview.org/t/catalystv2-field-data-array-name-causing-issues/10308
**Category:** In Situ Support
**Created:** [September 13, 2022, 7:55pm UTC](https://discourse.paraview.org/t/catalystv2-field-data-array-name-causing-issues/10308 "2022-09-13T19:55:20Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Andy\_Bauer](https://discourse.paraview.org/user_avatar/discourse.paraview.org/andy_bauer/32/5442_2.png) [@Andy\_Bauer](https://discourse.paraview.org/u/Andy_Bauer)
#### Post date: [September 13, 2022, 7:55pm UTC](https://discourse.paraview.org/t/catalystv2-field-data-array-name-causing-issues/10308/1 "2022-09-13T19:55:20Z")

</div>

The CatalystV2 is producing the channel field data attribute and calling it `channel`. Before in legacy Catalyst this string array was named ` __CatalystChannel__ `. This is causing issues when trying to generate valid new Catalyst Python scripts in the GUI since the channel name is not being automatically recognized when loading Catalyst generated data extracts.

I don’t know if it’s better to have duplicate field data arrays (`channel` and ` __CatalystChannel__ `) or just fix this and use the historical ` __CatalystChannel__ `.

Either way, this seems like something that should be addressed before the v5.11 release since the generated scripts won’t work as nicely without the user manually naming the sources in the GUI pipeline browser.

I created a gitlab issue at [https://gitlab.kitware.com/paraview/paraview/-/issues/21553](https://gitlab.kitware.com/paraview/paraview/-/issues/21553)