Add a "fixed decimal" currency friendly data type

[mwiegand]

Hi @nan,

@nan

For example, backwards compatibility—i.e., keeping existing workflows running—is very important to us.

I have worked with a client who decided to switch to Alteryx. I wonder why? One significant risk to workflow stability is using outdated software. This can happen when software is not regularly updated or when deprecated nodes continue to be used, undermining developers’ efforts to maintain current code. One example could be:

Update iframe Resizer from 3.5.1 to 4.3.9 to improve report designs

Hi, I am struggling to get the charts, in particular the line chart, fit to the report size. The x-axis is, regardless of the chosen format, always cut off. This applies to the interactive view as well as generated PDF files. [image] [image] Playing around with “additionalStyles” showed that the iframe does not scale properly. Tampering then with advanced layouting, in particular the iframe-resizer library, it didn’t improve. https://docs.knime.com/latest/analytics_platform_components_gui…

The dogma of “endless backwards compatibility” will cause more harm than good. I once inquired about the “exit strategy” for deprecated nodes and the influx of new chart nodes but did not receive a clear answer.

This leads me to another point:

@nan

a vision and strategy for our product

KNIME sometimes feels like it lacks a clear vision, especially since the integration of the Modern UI. This, along with the new columnar-based backend, gives the impression of a company still finding its direction. This might be more of a communication issue in explaining KNIME’s vision effectively.

To summarize, here are some key areas of concern:

1. Modern vs. Classic UI
2. Row vs. Columnar Based Backend
3. The numerous chart nodes
4. The shortcomings of these nodes, following the 80-20 rule, with basic features still missing months, if not years, later (similarly observed with the Modern UI)
5. Performance and reliability issues, as discussed in this thread

These points reflect actual perceptions. Providing a clearer picture of the vision would help put these issues into perspective.

Please note that my summary may seem critical, but in reality KNIME certainly is not in a bad situation. Feedback from power users, should be seen as a litmus test. We represent not only the general user base but also those who leverage KNIME at an enterprise level. Speaking about enterprises, their decision which tool to chose likely will be based on the word of mouth. Something KNIME has a clear edge with the community of any competitor.

As a closing point. There are many features and bugs reported but it’s unclear how many votes are necessary to gain sufficiently enough attention to get integrated or resolved. Like this topic which has eight votes, is open since years and, from perspective of many users, has both huge potential to improve reliability and therefore the chance of KNIME being utilized in enterprises more frequently. What is the vision about this?

Cheers
Mike