# Column Filter (PMML) not getting desired output in PMML tranformation apply **URL:** \ **Category:** KNIME Analytics Platform\ **Tags:** bug\ **Created:** [July 25, 2022, 1:41pm UTC](https://forum.knime.com/t/column-filter-pmml-not-getting-desired-output-in-pmml-tranformation-apply/45431 "2022-07-25T13:41:59Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![mlauber71](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mlauber71/32/73590_2.png) [@mlauber71](https://forum.knime.com/u/mlauber71)\ **Post date:** [August 2, 2022, 7:49am UTC](https://forum.knime.com/t/column-filter-pmml-not-getting-desired-output-in-pmml-tranformation-apply/45431/5 "2022-08-02T07:49:58Z")
@JoergWas, @nik_09 there is this discussion about PMML. Unfortunately the collection ofr PMML and models does not work as intuitively as one might hjope. But you still can use the transformations one at a time. At certain points you might have to do the filtering of transformed columns yourself I noticed: > [@When to use PMML model appender and PMML transformation appender?](https://forum.knime.com/t/when-to-use-pmml-model-appender-and-pmml-transformation-appender/44890/7): > > Hi, Thanks @mlauber71. I had a look at the workflow and I think I know what the main problem is: the Column Filter (PMML) filters the Data Dictionary of an incoming PMML document and outputs that, but PMML does not have any specification for filtering columns. So the new PMML created by the node does not really document the removal of columns, it just deletes every mention of them from the spec of the input data (the DataDictionary). It also keeps the TransformationDictionary as-is, so now the … --- _[View the full topic](https://forum.knime.com/t/column-filter-pmml-not-getting-desired-output-in-pmml-tranformation-apply/45431)._