# New Binner breaks backwards compatibility

**URL:** <https://forum.knime.com/t/new-binner-breaks-backwards-compatibility/91081>\
**Category:** Feedback & Ideas\
**Tags:** regression\
**Created:** [December 25, 2025, 12:17pm UTC](https://forum.knime.com/t/new-binner-breaks-backwards-compatibility/91081 "2025-12-25T12:17:32Z")\
**Posts on this page:** 2\
**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:** [December 25, 2025, 12:17pm UTC](https://forum.knime.com/t/new-binner-breaks-backwards-compatibility/91081/1 "2025-12-25T12:17:32Z")

</div>

Hi,

I notice just today that the Auto-Binner got deprecated not giving us a chance, during the Community Hacking Days, to assess it.

> [@Binner: Format quantiles number as float, not int](https://forum.knime.com/t/binner-format-quantiles-number-as-float-not-int/91079):
>
> Hi, the binner nodes UI got transitioned to MUI. When swithcing to quantiles the zero is presented asn an int, encouraging to assume and to type iont instead of floats. I’d like to propose to dispaly it a sfloat directly, though. Best Mike

Upon closer inspection I find the new UI rather confusing.

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/4/6/468bbe455d1b8bafb1b11b9c87cea52d70317d73.png)

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

Though, I noticed when trying to replicate the exact quantile setup I usually use to identify the lower and upper 5 %, that the lower and upper outlier get named differently and there is no options to disable it

| Universe\_0\_0 | Universe\_0\_0 [Binned] | Universe\_0\_0 (#1) | Universe\_0\_0 (Binned) |
| --- | --- | --- | --- |
| 3.1954722290339355E-5 | Bin 1 | 3.1954722290339355E-5 | Lower outlier |

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/a/6/a61ae107480e651020853abadb6e5c511a2c7c7a.png)

This can break backwards compatibility and I cannot imagine a reason for this deviation. Here is the test workflow:

> **[91081 - New Binner breaks backwards compatibility – mwiegand](https://hub.knime.com/mwiegand/spaces/Public/Bugs/91081%20-%20New%20Binner%20breaks%20backwards%20compatibility~qnyA3L1dHik-j9ZQ/current-state)**
>
> Solutions for data science: find workflows, nodes and components, and collaborate in spaces.

Best  
Mike

---

<div class="post-metadata">

**Author:** ![ActionAndi](https://forum-cdn.knime.com/user_avatar/forum.knime.com/actionandi/32/76198_2.png) [@ActionAndi](https://forum.knime.com/u/ActionAndi)\
**Post date:** [December 29, 2025, 10:02am UTC](https://forum.knime.com/t/new-binner-breaks-backwards-compatibility/91081/2 "2025-12-29T10:02:09Z")

</div>

And in addition to it coming from this:

 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/7/c/7ce6f8434bc897da96f247ef64e6189767366331.png)  
to this:  
 ![image](https://forum-cdn.knime.com/uploads/default/original/3X/2/d/2d257bf446dac575edeacdb28e91c06fb5f43b6c.png)

is just a nightmare regarding usablitity:
